/programs/auth/userdeprecatedThis endpoint is deprecated. Scheduled for removal on 2026-03-01.
Create new auth user
DEPRECATED, use /programs/{program_id}/frameworks/{framework_id}/auth/users instead. Creates a new user in OptiTech Auth.
The user will be created in your neon_auth.users_sync table and automatically propagated to your auth program, whether OptiTech-managed or provider-owned.
Quick start
curl "https://api.optitech.com/v1/programs/auth/user" \
-X POST \
-H "Authorization: Bearer $OPTITECH_API_KEY"import { createOptiTechClient, raw } from '@optitech/sdk';
const optitech = createOptiTechClient({ apiKey: process.env.OPTITECH_API_KEY });
const { data } = await raw.createNeonAuthNewUser({
client: optitech.client
});Request body
3 required Required: program_id, auth_provider, email.
program_idauth_provideremail≥1 chars, ≤256 chars
name≥1 chars, ≤255 chars
Response
201Creates new user
Errors
General error
This endpoint can return the standard OptiTech 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.