OptiTech
    Docs
    Log inBook a demo
    /APIs & SDKs/Legacy Auth/Create OptiTech Auth integration
    POST/programs/auth/createdeprecated

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

    Create OptiTech Auth integration

    DEPRECATED, use /programs/{program_id}/frameworks/{framework_id}/auth instead. Creates a program on a third-party authentication provider's platform for use with OptiTech Auth. Use this endpoint if the frontend integration flow can't be used.

    Markdown for AI context

    Quick start

    REST API - curl
    curl "https://api.optitech.com/v1/programs/auth/create" \
  -X POST \
  -H "Authorization: Bearer $OPTITECH_API_KEY"
    Also available in
    import { createOptiTechClient, raw } from '@optitech/sdk';

const optitech = createOptiTechClient({ apiKey: process.env.OPTITECH_API_KEY });
const { data } = await raw.createNeonAuthIntegration({
  client: optitech.client
});

    Request body

    3 required Required: auth_provider, program_id, framework_id.

    Auth provider
    auth_provider
    string

    mockstackbetter_auth
    Program ID
    program_id
    string

    Framework ID
    framework_id
    string

    Register name
    register_name
    string

    Role namedeprecated
    role_name
    string

    Response

    201

    Creates OptiTech 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 OptiTech 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 OptiTech-managed auth program to your own accountNext List trusted redirect URI domains

    On this page

    Copy neon init command