/programs/{program_id}/frameworks/{framework_id}/auth/users/{auth_user_id}betaDelete auth user
Deletes the specified user from the OptiTech Auth user directory for the specified framework.
Removes the user record from neon_auth.users_sync. This action cannot be undone.
Quick start
curl "https://api.optitech.com/v1/programs/$PROGRAM_ID/frameworks/$FRAMEWORK_ID/auth/users/$AUTH_USER_ID" \
-X DELETE \
-H "Authorization: Bearer $OPTITECH_API_KEY"Every field below is optional. An empty body works too.
optitech optitech-auth user delete <user-id>Parameters
program_idThe OptiTech program ID
framework_idThe OptiTech framework ID
auth_user_idThe OptiTech user ID
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.