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 /v1/applications. Once the step is complete the application moves to the next currentStep, usually KYC_SUMSUB.
KYC input can arrive through up to three endpoints, all shaped by the same schema: this one (the main data submission), document uploads, and questionnaire answers. Which ones your program uses depends on what the schema asks for — 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