Get customer requirements
Retrieve a requirements view of a customer:
four buckets — complete, pending, missing, issues — plus a
coarse requirements_due summary of categories that still need
attention. Each requirement carries a stable typed code (switch on
this) and, when available, a verbatim description from the upstream
KYC provider’s moderation comment. NOTE: The description field is subject to change without notice.
Computed on demand from the customer’s identifications and customer-level state; no separate ingestion step is needed.
Authorizations
API Key
Headers
Optional sub-partner UUID, if provided, the customer will be filtered for the sub-partner
Selects the API version for this request, as an ISO date (YYYY-MM-DD). Omit to use the default version (2025-03-13). Supported versions: 2025-03-13, 2026-07-01.
Path Parameters
the ID of the Customer to GET requirements for
Response
GET Customer Requirements Succeeded
Bridge-style requirements view of a customer. All four buckets are
always present (may be empty). requirements_due is a quick coarse
summary — partners can use it to decide whether any action is needed
before drilling into the detail buckets.
Requirements the customer has satisfied.
Submitted requirements that were rejected or could not be processed.
Inspect retryable to distinguish correctable from terminal issues.
Requirements the customer has never submitted.
Requirements the customer has submitted, awaiting review.
Sorted, deduplicated set of categories that have at least one non-complete item. Empty for fully-onboarded customers.
Coarse summary of which areas of the customer's Sumsub KYC/KYB process
still need attention. Used as a quick filter — full detail lives in the
four complete/pending/missing/issues buckets.
kyc, kyb 
