POST
Submit KYC data
Submit the user’s answers, keyed against the schema. Partial saves are allowed; the response’s isComplete says whether the step is finished, and field validation failures come back with code: VALIDATION_ERROR. Keep polling GET /v2/applications. Right after a complete submission currentStep is PROCESSING with no requiredActions while we process the form: show a loader, don’t show the form again. Then the application moves to the next currentStep, usually IDENTITY_VERIFICATION. (On GET /v1/applications the form step stays for those few seconds, so keep a loader up after a successful submit until currentStep changes.)
KYC input is shaped by your program’s KYC schema. Submit the field answers here (the main data submission); any documents the schema asks for are uploaded via a presigned URL. Drive it from the schema, not assumptions. For companies, the main submission goes to KYB submit instead.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

applicationId
string
required

The unique identifier of the application.

Query Parameters

programId
string
required

The program the application/customer belongs to. Appended as a query parameter on every back-office request.

Body

application/json

The dynamic onboarding answer payload. Field answers keyed by the schema field key, or steps of { key, data } pairs matching the layout returned by the onboarding schema. Values are strings, nested groups, or base64url-encoded file contents.

Response

KYC data accepted.

success
boolean
Example:

true

data
object