Skip to main content
POST
Create a customer

Authorizations

Authorization
string
header
required

Token from POST /auth/token

Headers

Idempotency-Key
string
required

Unique key to prevent duplicate requests. Required on all POST requests.

Body

application/json

Create a new individual customer. Almost all fields are optional — only type is required. PII fields (birthDate, residentialAddress, ipAddress, identifyingInformation) are write-only and never returned in responses.

type
enum<string>
required

Must be "individual". Only valid option for MVP.

Available options:
individual
Example:

"individual"

firstName
string

Customer's legal first name.

Example:

"Jane"

middleName
string

Customer's middle name.

lastName
string

Customer's legal last name.

Example:

"Smith"

email
string<email>
Example:

"jane@example.com"

phone
string

Primary phone in E.164 format.

Example:

"+12125551234"

birthDate
string
write-only

Date of birth in YYYY-MM-DD format. Write-only.

Example:

"1990-05-15"

nationality
string

ISO 3166-1 alpha-2 country code.

Example:

"US"

ipAddress
string
write-only

End-user's IP address. Used for geo-based compliance checks on the basic endorsement. Write-only.

externalId
string

Developer's own user ID for cross-referencing.

Example:

"usr_12345"

signedAgreement
boolean
default:false

Whether the customer has accepted OMS terms of service. Default false.

residentialAddress
object

Customer's residential address. Write-only.

identifyingInformation
object[]
write-only

Array of ID documents. Write-only. Supported types: ssn, itin, driversLicense, passport.

endorsements
enum<string>[]

Endorsements to request: basic, cryptoCustody, usd. If omitted, OMS defaults to cryptoCustody and usd (which auto-includes basic).

Available options:
basic,
cryptoCustody,
usd
metadata
object | null

Response

Customer created

Customer response object. PII fields (birthDate, residentialAddress, ipAddress, identifyingInformation) are write-only — accepted in POST/PATCH but never returned in responses.

id
string
Example:

"cst_01H9Xa8F5dN6mP3q"

object
string
Example:

"customer"

type
enum<string>

Customer type. Only individual is supported for MVP.

Available options:
individual
Example:

"individual"

firstName
string | null
Example:

"Jane"

middleName
string | null
Example:

null

lastName
string | null
Example:

"Smith"

email
string | null
Example:

"jane@example.com"

phone
string | null

Primary phone in E.164 format.

Example:

"+12125551234"

nationality
string | null

ISO 3166-1 alpha-2 country code.

Example:

"US"

externalId
string | null

Developer's own user ID for cross-referencing.

Example:

"usr_12345"

status
enum<string>

active or inactive. Inactive customers cannot create new transactions. No intermediate states — all granularity lives in endorsement statuses.

Available options:
active,
inactive
Example:

"active"

signedAgreement
boolean

Whether the customer has accepted OMS terms of service.

Example:

true

signedAgreementAt
string<date-time> | null

Timestamp when signedAgreement was set to true. Null if not yet signed.

Example:

"2026-03-20T14:15:22Z"

wallets
object[]

Simplified flat view: one entry per wallet-asset combination. Use GET /wallets/{id} for the full representation.

endorsements
object[]

Endorsements track KYC/compliance status. Types: basic, cryptoCustody, usd. Statuses use SCREAMING_CASE: INACTIVE, PENDING, ISSUES, ACTIVE, REJECTED, REVOKED_ISSUES, OFFBOARDED.

metadata
object | null
createdAt
string<date-time>
updatedAt
string<date-time>