/{app_slug}/v1/admin/usersAuthProvision a new end-user
Create an account in this app. Distinct from the public `/auth/signup`: no session is issued, no password is required (when omitted, the customer triggers a password-reset to finish onboarding), and the primary email contact starts unverified — the customer is responsible for kicking off the verification flow via `/auth/request-verification` or `/auth/send-verification-email`. The `roleName` defaults to the app's `signup_default_role`. What is NOT distinct: the password policy. A supplied `password` goes through the same app-configured rules, the same common-password deny-list and the same breach check as `/auth/signup`.
Path parameters
app_slug*stringSlug of the app.
Headers
Idempotency-KeystringRetry safety: a repeat with the same key and body replays the first response instead of creating a user again. Same key with a different body: 409 `IDEMPOTENCY_KEY_REUSE`. 24 h window.
Request body
email*stringPrimary email — becomes the account's primary email contact (unverified).
Example: "ada@example.com"
usernamestringUsername inside the app. Derived from the email local-part if omitted.
Example: "john_doe"
display_namestringHuman-readable display name.
passwordstringOptional initial password. When omitted, the account has no credential — the customer triggers the password-reset flow to onboard the user. When supplied it must satisfy the SAME rules as `/auth/signup`: the app-configured length and character classes, the common-password deny-list (400 `PASSWORD_TOO_COMMON`) and, unless the app sets `password_breach_check` to `off` or `warn`, the breach corpus (400 `PASSWORD_BREACHED`).
role_namestringRole to assign. Defaults to the app's `signup_default_role`.
Response · 201 Created end-user record.
id*stringUnique identifier of the user.
username*stringThe end user's username, unique within the app.
display_name*stringHuman-readable name of the user.
email*stringEmail address.
email_verified*booleanWhether the email address was marked verified at creation.
role*stringApp-level role name of the user, or `null` for none.
status*stringAccount status: `active`, `suspended` or `deactivated`.
created_at*string · date-timeWhen the user was created (ISO 8601).
password_warningsarrayPresent only when the app runs `password_breach_check: 'warn'` and the supplied password was found in the breach corpus. The account IS created; in `'block'` mode the request would have been rejected with 400 `PASSWORD_BREACHED` instead. Same shape as the signup response.
Example: ["breached"]
Example
Request
POST https://api.auth.productcraft.co/{app_slug}/v1/admin/users
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json
{
"email": "ada@example.com",
"username": "john_doe",
"display_name": "string",
"password": "string",
"role_name": "string"
}Response
{
"id": "string",
"username": "string",
"display_name": "string",
"email": "string",
"email_verified": false,
"role": "string",
"status": "string",
"created_at": "2026-01-01T00:00:00.000Z",
"password_warnings": [
"breached"
]
}