Advance the user application
Advances the user KYC application. Only valid while the application is in a pending state. Which verification method applies is fixed by your project configuration rather than chosen per request, and determines the request you send. With no body (Reap-run verification), Reap returns a provider SDK token in nextAction for the client to complete and approval arrives later via webhook. For an externally-completed verification (e.g. a Sumsub applicant share token), the submission is ingested synchronously and approves the user. For a full verified data pack, the response nextAction lists the supporting documents to upload via POST /users/:id/application/documents. Send an Idempotency-Key to safely retry without re-consuming a single-use share token.
Authorizations
API key as Bearer token
Headers
API version (YYYY-MM-DD)
2025-02-14 "2025-02-14"
Unique key for safely retrying this request. Up to 255 characters; we recommend a UUIDv4. The first request executes and its response is cached; subsequent requests with the same key replay the cached response (24h retention).
1 - 255Path Parameters
User ID
Body
How to advance the KYC application. The accepted methods depend on the project KYC integration mode; each method is a distinct variant selected by the method field.
- Managed KYC
- Sumsub Token Sharing
- Universal KYC
"MANAGED_KYC"Response
Application state after advancing
Current KYC application status
NOT_STARTED, AWAITING_DOCUMENTS, IN_REVIEW, APPROVED, REJECTED, RETRY_REQUIRED "NOT_STARTED"
Action the client must take next, or null if none remains
- ProviderSdk
- DocumentUpload
Deprecated: use nextAction.provider. Populated only when nextAction.type is PROVIDER_SDK.
"sumsub""sumsub"
Deprecated: use nextAction.sdkToken. Populated only when nextAction.type is PROVIDER_SDK.
"_act-sbx-abc123-xyz789"