Skip to main content
Neon Docs

Search documentation

Type to search this documentation.

Disable Neon Auth for the branch

DELETE/projects/{project_id}/branches/{branch_id}/authDisable Neon Auth for the branch

Disables the Neon Auth integration for the specified branch, removing the connection to the authentication provider. If delete_data is true, also deletes the neon_auth schema and all associated tables from the branch database. The integration can be re-enabled by calling POST /projects/{project_id}/branches/{branch_id}/auth.

Parameters

project_idstringpathrequired

The Neon project ID

pattern ^[a-z0-9-]{1,60}$

branch_idstringpathrequired

The Neon branch ID

pattern ^[a-z0-9-]{1,60}$

Request body

application/json
object
delete_databoolean

If true, deletes the `neon_auth` schema from the database

default false

Example request
{
  "delete_data": false
}

Responses

200Delete the integration with the authentication provider
defaultGeneral Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress. application/json
objectGeneralError
codestringrequired

default ""

messagestringrequired

Error message

request_idstring

Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.

Example response
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
Documentation menu