Drives KYB, KYC, or applicant account status through a sandbox transition without waiting for real compliance review. Available in sandbox mode only.
Type → effect mapping:
| type | KYB status set | Application status set | webhooks emitted |
|---|---|---|---|
kyb_approve | approved (via provisioning) | approved | 2× customer.kyb_status.created (one per provider, kyb_status: approved) + recipient.created |
kyb_reject | — | declined | (none — application status only) |
kyb_info_request | — | request_for_information | (none — application status only) |
kyc_approve | — | approved | (none — application status only) |
kyc_reject | — | declined | (none — application status only) |
kyc_info_request | — | request_for_information | (none — application status only) |
applicant_activate | approved (via provisioning) | approved | 2× customer.kyb_status.created (one per provider, kyb_status: approved) + recipient.created |
applicant_suspend | — | declined | (none — application status only) |
Approving customers (individual or business): Use kyb_approve to fully approve
any customer type. This triggers the complete onboarding flow including endorsement
and recipient creation. The kyc_* types only update the individual applicant’s
KYC application status without triggering the full onboarding flow.
Note: applicant_activate does NOT auto-create payment accounts, wallets, or
account numbers. Create those separately via the account creation API after activation.
Documentation Index
Fetch the complete documentation index at: https://docs.dakota.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Unique key to ensure request idempotency. If the same key is used within a certain time window, the original response will be returned instead of executing the request again.
The onboarding transition to simulate
kyb_approve, kyb_reject, kyb_info_request, kyc_approve, kyc_reject, kyc_info_request, applicant_activate, applicant_suspend The onboarding application ID (from POST /applications)
"01H..."
Unique ID for this simulation (for idempotency and tracing)
1 - 128"sim_03H..."
Organization ID (for context; optional, used for logging)
"org_01H..."
Optional reason code for reject/info_request transitions
"MISSING_EIN"
Fields to request (for *_info_request types only)
["ssn", "address"]