/projects/{project_id}/branches/{branch_id}/auth/oauth_providers/{oauth_provider_id}betaUpdate OAuth provider
Updates an OAuth provider for the specified project.
Quick start
curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/branches/$BRANCH_ID/auth/oauth_providers/$OAUTH_PROVIDER_ID" \
-X PATCH \
-H "Authorization: Bearer $NEON_API_KEY"neon neon-auth oauth-provider update --provider-id <provider-id>Parameters
project_idThe Neon project ID
branch_idThe Neon branch ID
oauth_provider_idThe OAuth provider ID
Request body
No field is required.
client_idThe OAuth client ID registered with the provider. Omit to keep the currently configured value.
client_secretOAuth client secret for the provider. Omit to leave the existing secret unchanged.
microsoft_tenant_idThe tenant ID scoping the Microsoft OAuth provider. Supply this field when the provider type is microsoft; it has no effect for other provider types.
Response
200The OAuth provider has been added to the project
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.