/projects/auth/transfer_ownershipTransfer Neon-managed auth project to your own account
Transfers ownership of your Neon-managed auth project to your own auth provider account.
Quick start
curl "https://console.neon.tech/api/v2/projects/auth/transfer_ownership" \
-X POST \
-H "Authorization: Bearer $NEON_API_KEY"import { createApiClient } from '@neondatabase/api-client';
const api = createApiClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await api.transferNeonAuthProviderProject({});Request body
2 required Required: project_id, auth_provider.
project_idauth_providerResponse
200Transfer initiated. Follow the URL to complete the process in your auth provider's UI.
Errors
General error
This endpoint can return the standard Neon API error response.
Response fields
messageRequired. Human-readable error message.codeRequired. Machine-readable error code.request_idOptional. Request identifier for debugging. You can provide one with theX-Request-IDheader.
Retry guidance
If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.
Idempotent methods (GET, HEAD, OPTIONS) are generally safe to retry after a network error or timeout. Non-idempotent methods (POST, PATCH, DELETE, PUT) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.
Responses with 423 Locked or 503 Service Unavailable are safe to retry. 423 Locked means the resource is temporarily locked, usually because another operation is in progress.