Discover feature requirements for a customer
Same response shape as GET /v2/onboarding/requirements, resolved as a delta against what the customer already has on file. country echoes the customer’s registered country. Returns 422 ONBOARDING_NOT_READY if the customer has no business record yet.
Authorizations
Path Parameters
Query Parameters
Feature whose requirements you want to discover.
VIRTUAL_ACCOUNT, CRYPTO_WALLET, WALLET_CUSTODY_CONVERSION Response
Discovery response schema version. Bumps on any breaking discovery-response change (field renamed, removed, type changed, conditional semantics changed). Distinct from the webhook envelope's apiVersion which tracks the API major. Clients pin the literal and fail loudly on mismatch; servers do not negotiate.
3 The discovery context that produced this requirements set.
onboarding, feature, order "onboarding"
ISO 3166-1 alpha-3 country code the requirements were resolved for. Always three uppercase letters.
^[A-Z]{3}$"USA"
Scalar fields the integrator must collect, with format hints and allowedValues for enum fields.
Customer-level documents to collect. Each row is keyed by canonicalType; upload every requiredArtifacts[] entry and any one alternatives[] entry when present, otherwise upload the row itself via POST /v2/documents.
Per-role count and person-level field + document requirements for ownership.persons[].
- Option 1
- Option 2