Skip to main content
POST
Create a KYC submission with API data

Authorizations

Authorization
string
header
required

Session JWT (from register/login) or API key (pk_...). X-API-Key: <token> is accepted as an alternative header.

Body

application/json
external_customer_id
string
required

Your reference for the verified customer.

idempotency_key
string
required
person
object

Person fields (first_name, last_name, email, phone, nationality, date_of_birth, tax_id, id_type, id_number, address, primary_purpose, most_recent_occupation, source_of_funds).

metadata
object

Response

Submission created (enters the compliance review queue).

submission_id
string<uuid>
kind
enum<string>
Available options:
kyc,
kyb
external_customer_id
string
status
enum<string>
Available options:
pending_review,
in_review,
changes_requested,
more_info_required,
escalated,
approved,
approved_partial,
rejected
risk_band
string
liveness_pending
boolean

KYC only. True until the video liveness check passes.

pending_documents
string[]
rejection_reason
string
aml_decision
string

KYB only.

verification_fee
string
idempotency_key
string
created_at
string<date-time>
updated_at
string<date-time>
Last modified on July 18, 2026