Oveview
This method is used by partners to import shared applicants for Reusable KYC.
Request example
curl -X POST \
'https://api.sumsub.com/resources/api/reusableIdentity/reuse?shareToken=_act-jwt-eyJhbGciOiJub25lIn0.eyJqdGkiOiJfYWN0LTE3YjM5YTljLWRhOWUtNGY2MS04Y2ZjLTYwNzViNWM2NDk5MSIsInVybCI6Imh0dHA6Ly9sb2NhbGhvc3Q6ODA5MCJ9.&levelName=liveness-id-poa'
Response explained
If the Donor profile contains any data that satisfies the requirements of the Recipient level, a new applicant ID is generated and the corresponding applicant object is returned.
{
"id": "689223ed75b5d1bc2bb38gdg",
"createdAt": "2025-08-05 15:31:57",
"clientId": "DonorCompany",
"externalUserId": "copy-4ba4dfa5-ff31-43d4-b612-111d1111aa9",
"info": {
"firstName": "John",
"firstNameEn": "John",
"lastName": "Smith",
...
}
In case no data from the Donor profile meets the requirements of the Recipient level, or if another error occurs, the method returns an error response. You can see possible errors with descriptions in the table below.
Note
If a token is malformed or expired, generic token-related errors may be returned, including a
401 Unauthorizedresponse.
Error response examples
You may encounter two categories of errors. Generic token validation occurs first and may return a 401 Unauthorized. If token validation succeeds, the endpoint may return a 400 error with a specific error code indicating the underlying problem.
{
"code": 401,
"description": "Token is invalid: Token _act-374dc16e-4c7e-4e50-a621-ed76a0dd68fb-v2 is invalid now: created at Tue Dec 02 08:27:46 UTC 2025 with ttl 5 but accessed at Tue Dec 02 08:29:55 UTC 2025 [source: null]",
"type": "de.smtdp.commons.service.exceptions.ServiceException"
}
{
"code": 400,
"errorCode": 10513,
"errorName": "reusable-kyc-not-compatible-doc-type",
"description": "Not Reusable KYC for level: id-liveness-preview",
"type": "de.smtdp.commons.service.exceptions.ServiceException"
}
Error codes with descriptions
| Error code | Error name | Description |
|---|---|---|
| 10501 | not-in-partners-list | Reusing applicants is not allowed since the target is not your partner. |
| 10502 | invalid-partner-id | The partner ID extracted from the share token is invalid. |
| 10503 | invalid-share-token | The provided share token is malformed or expired. |
| 10504 | non-suitable-share-token | The share token is not suitable for reuse with the given level. |
| 10505 | reusable-kyc-disabled | Reusable KYC functionality is disabled. |
| 10506 | reusable-kyc-not-reusable | The donor applicant does not meet reuse eligibility criteria. This is a generic fallback error used when a more specific cause is not available. |
| 10507 | reusable-kyc-not-approved-applicant | The donor applicant is not in an approved state. |
| 10508 | reusable-kyc-not-active-applicant | The donor applicant is not in an active state. |
| 10509 | reusable-kyc-not-kyc-moderation-type | The moderation type of the source KYC is not suitable for reuse. |
| 10510 | reusable-kyc-not-selfie-or-identity-doc | Required selfie or identity document is missing. |
| 10511 | reusable-kyc-not-selfie-liveness | Liveness is required but not satisfied by the source data. |
| 10512 | reusable-kyc-not-req-doc-overlap | Required document types do not overlap between source and target levels. |
| 10513 | reusable-kyc-not-compatible-doc-type | Provided document types are not compatible with target level requirements. |
| 10514 | reusable-kyc-not-actual-poi-date | Proof of Identity is outdated and not valid for reuse. |
| 10515 | reusable-kyc-not-actual-poa-date | Proof of Address is outdated and not valid for reuse. |
| 10516 | reusable-kyc-not-acceptable-age | The applicant does not meet the required age criteria. |
| 10517 | reusable-kyc-incompatible-capture-settings | Capture settings mismatch between donor and recipient requirements. |