This endpoint is useful for checking the KYC status after the user has completed the verification process.
🔐 Headers
| Header | Description |
|---|---|
partner-api-key | API key associated with your partner account. Required. See API Key Generation Guide. |
This endpoint requires authentication using a valid
partner-api-key.📥 Query Parameters
Field | Type | Required | Description |
|---|---|---|---|
userId | string | ✅ | The ID of the user for whom to retrieve KYC verification details. |
📘 Example Request
📤 Response Body
The response will include all available verification information, including face match results, fraud checks, ID document data, and AML results.⚠️ Important Notes & Requirements
- Partner API Key is mandatory: All requests must include a valid
PartnerApiKeyin the header. Get your API key. - User must exist: The provided
userIdmust reference a user that was created using the Create User endpoint. - Session Completion Required: Verification results are only available after the user has completed the full KYC session.
- Partial Data Possibility: Depending on the verification provider and user input, some fields in the response may be missing or marked as null.
- No Side Effects: This endpoint is read-only and does not trigger any updates or notifications.
- Compliance Responsibilities: It’s up to each partner to determine how to act upon the returned verification and AML data.
- Retry Strategy: If the session has expired or was inconclusive, a new verification session should be initiated using the KYC Link Generation endpoint.
✅ Use Cases
-
Compliance Review
After the user finishes KYC, partners can retrieve all details (ID, liveness, AML, etc.) for internal or regulatory review. -
Automated Decisioning
Use face match scores, ID info, and fraud signals to automatically determine onboarding acceptance. -
Support Investigation
In cases of dispute or manual review, support agents can inspect full verification artifacts using this data. -
AML Screening Integration
CombineamlInforesults into your internal or third-party AML workflows to comply with regional regulations.
Headers
Api key for the affiliated partner that is performing the request
Query Parameters
The user ID
Example:
"2a119021-ed39-4ab4-8690-db610c53f0fb"