Get Current KYC Validation
Session-based validation
Get Current KYC Validation
Retrieve the current active KYC validation for an entity — in the gu1 KYC API for identity verification flows, with examples for current validation use cases.
GET
Get Current KYC Validation
Overview
This endpoint retrieves the current active KYC validation for a specific entity. The “current” validation is the most recent validation marked withisCurrent: true.
Key features:
- Returns the active validation for an entity
- Automatically syncs with the KYC provider if images are expired (> 3.5 hours)
- Includes all verification data (documents, biometrics, risk assessment)
- Returns 404 if no current validation exists
When to Use This
- Check verification status: See if an entity has an active KYC validation
- Display verification data: Show document and biometric verification results in your UI
- Validate user identity: Check if a user has completed KYC before allowing certain actions
- Compliance checks: Verify that an entity has valid KYC documentation
Request
Endpoint
Path Parameters
The ID of the entity to get the current validation for
Headers
Response
Success Response (200 OK)
Returns the current validation object with all verification data:Example Request
Status Values
The responsestatus field can be one of:
pending- Validation created, customer hasn’t startedin_progress- Customer is completing verification (filling out form)in_review- Verification completed, requires manual review from compliance teamapproved- Verification successful (by provider or manually)rejected- Verification failed (by provider or manually)expired- Validation expired (customer didn’t complete in time)abandoned- Customer started but didn’t completecancelled- Validation manually cancelled
Error Responses
No Current Validation Found (404)
- Has never had a KYC validation created
- Has validations, but none are marked as current (
isCurrent: false) - All validations are in terminal states (cancelled, expired, etc.)
Entity Not Found (404)
Important Notes
Auto-Sync with Provider
Auto-Sync with Provider
If the validation images are older than 3.5 hours, this endpoint automatically syncs with the KYC provider to refresh the data. This ensures you always get fresh verification images and data.
Current vs Historical Validations
Current vs Historical Validations
Only one validation per entity can have
isCurrent: true at a time. When a new validation is created, the previous current validation is automatically marked as not current. Use the /api/kyc/entities/:entityId/validations endpoint to retrieve historical validations.Status Values
Status Values
Possible status values:
pending: User hasn’t started verification yetin_progress: User is completing verification (has some data but not finished)approved: Verification approved (by provider or manually)rejected: Verification rejected (by provider or manually)cancelled: Validation was cancelledexpired: Validation expired (user didn’t complete in time)abandoned: User started but abandoned the verification process
Manual Status Protection
Manual Status Protection
If a validation has been manually approved, rejected, or cancelled, it will NOT be updated by provider webhooks or sync operations. Manual decisions are protected to maintain audit trail integrity.
Next Steps
Create KYC Validation
Start a new verification session
List All Validations
View validation history for an entity
Sync Validation
Manually refresh validation data
Approve Validation
Manually approve a validation