Start a verification
Starts a customer’s verification once the customer meets its requirements. See Business verification and Individual verification for what each customer type needs.
BUSINESS customers must start their verification with this route. INDIVIDUAL customers complete it by opening verification.link, except individuals in RFI and individuals created with a Sumsub shareToken, who start it here.
To verify only some associated parties again without restarting the customer’s verification, send associatedPartyIds. See Retrying verification for specific associated parties.
Authorizations
Bearer authentication header on the format Bearer <API_KEY>.
Headers
Optional idempotency key: any string, a UUID v4 is recommended. Resending the same key with a different request body is a conflict. Cached responses include the header X-Idempotent-Cached: true. Keys expire after 24 hours.
Path Parameters
Customer's unique identifier.
Body
Associated parties to verify again. Requires a previous verification. Only for BUSINESS customers, and for parties in RFI.
1Associated party's unique identifier (UUID v4).
Response
Verification successfully started.
Verification's unique identifier. Read it with GET /customers/{id}/verifications/{verificationId}.
"f95b288c-e77a-4553-9f29-2ca0ea485eb2"