---
title: "Delete integration with auth provider"
method: DELETE
path: "/projects/{project_id}/auth/integration/{auth_provider}"
tags: ["Auth (legacy)"]
deprecated: true
---

# Delete integration with auth provider

`DELETE /projects/{project_id}/auth/integration/{auth_provider}`

> **Deprecated.**

DEPRECATED, use `/projects/{project_id}/branches/{branch_id}/auth` instead.

## Path parameters

- `project_id` string, required
- `auth_provider` 'mock' | 'stack' | 'better_auth', required

## Request body

- object
  - `delete_data` boolean — If true, deletes the `neon_auth` schema from the database

## Response `200`

Delete the integration with the authentication provider

## Other responses

- `default` — General 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.

---

[API](https://skmtc.net/neon/apis/neon-api.md) · [All operations](https://skmtc.net/neon/apis/neon-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/neon/neon-api/revisions/cfde79a5c713/schema)