Skip to main content
POST
User Onboarding

Authorizations

x-api-key
string
header
required

API key for authentication. Must be included in the x-api-key header.

Body

application/json
first_name
string
required
Example:

"John"

last_name
string
required
Example:

"Doe"

email_address
string<email>
required
Example:

"user@example.com"

phone_number
string
required
Example:

"+1XXXXXXXXXX"

user_type
enum<string>
required
Available options:
individual
Example:

"individual"

date_of_birth
string<date>
required
Example:

"YYYY-MM-DD"

Example:

"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Example:

true

identity
object
required
address
object
required
metadata
string
Example:

"{}"

documents
AdditionalDocuments · object[]

Additional supporting documents for user onboarding. Can include various document types such as proof of address, source of funds, etc.

Response

User created successfully

id
string<uuid>

Unique user identifier

Example:

"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

status
enum<string>

Current user status. under_review: Initial status when user is created (default). active: User has been approved and verified. paused: User account is temporarily paused. rejected: User has been rejected during KYC process. offboarded: User has been removed/offboarded from the system. incomplete: User profile is missing required information.

Available options:
under_review,
active,
rejected,
offboarded,
incomplete
Example:

"under_review"

documents
object[]

List of uploaded documents (both identity and supporting documents)

Example:
address
object
first_name
string

User's first name

Example:

"John"

last_name
string

User's last name

Example:

"Doe"

email_address
string<email>

User's email address

Example:

"user@example.com"

phone_number
string

User's phone number

Example:

"+1XXXXXXXXXX"

date_of_birth
string<date>

User's date of birth

Example:

"YYYY-MM-DD"

rejection_reasons
object[] | null

Array of rejection reason objects (only populated for rejected users, null otherwise). Each object contains customer-facing reason, timestamp, and internal developer reason.

Example:

null

requirements
string[] | null

List of missing requirements for incomplete users (null when no requirements are missing)

Example:

null