Neon is expanding into a backend: Object Storage, Functions, and AI Gateway now in beta
Neon
    Docs
    Log inSign up
    /APIs & SDKs/Legacy Auth/Create Neon Auth integration
    POST/projects/auth/createdeprecated

    This endpoint is deprecated. Scheduled for removal on 2026-03-01.

    Create Neon Auth integration

    DEPRECATED, use /projects/{project_id}/branches/{branch_id}/auth instead. Creates a project on a third-party authentication provider's platform for use with Neon Auth. Use this endpoint if the frontend integration flow can't be used.

    Markdown for AI context

    Quick start

    REST API - curl
    curl "https://console.neon.tech/api/v2/projects/auth/create" \
  -X POST \
  -H "Authorization: Bearer $NEON_API_KEY"
    Also available in
    import { createNeonClient, raw } from '@neon/sdk';

const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.createNeonAuthIntegration({
  client: neon.client
});

    Request body

    3 required Required: auth_provider, project_id, branch_id.

    Auth provider
    auth_provider
    string

    mockstackbetter_auth
    Project ID
    project_id
    string

    Branch ID
    branch_id
    string

    Database name
    database_name
    string

    Role namedeprecated
    role_name
    string

    Response

    201

    Creates Neon Auth integration

    Depth
    "auth_provider": (string),reqmock | stack | better_auth
    "auth_provider_project_id": (string),req
    "pub_client_key": (string),req
    "secret_server_key": (string),req
    "jwks_url": (string),req
    "schema_name": (string),req
    "table_name": (string),req
    "base_url": (string),

    Errors

    default

    General error

    This endpoint can return the standard Neon API error response.

    Response fields

    • message Required. Human-readable error message.
    • code Required. Machine-readable error code.
    • request_id Optional. Request identifier for debugging. You can provide one with the X-Request-ID header.

    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.

    Was this page helpful?
    Previous Transfer Neon-managed auth project to your own accountNext List trusted redirect URI domains

    On this page

    Copy neon init command