GET
Requires kyc.read. This endpoint returns the backend-authoritative KYC form submission in a canonical { data, meta } JSON shape. Use it when an integration needs the customer’s submitted KYC form details without downloading a PDF export. File uploads and signatures are returned as opaque document/signature references with display names. The response does not expose storage keys.

Path parameters

string
required
The user ID whose submitted KYC form answers should be retrieved.

Returns

string | null
KYC submission record ID.
string
Always kyc_submission.
object
User, tenant, environment, and account-type identifiers for the submission.
object
Runtime form identity, version, and schema version pinned to the submission.
object
KYC submission status and timestamps.
object
KYC verification status and provider status metadata.
array
Submitted form sections. Each section contains ordered fields; grouped questions contain nested fields instead of flattening child answers into the top-level list.
object
Request metadata including requestId, apiVersion, and generatedAt.

Error codes

KYC form answers can contain regulated PII. Store and transmit this JSON according to your tenant retention policy and regional data-residency obligations.