Create a Document Validation
POST
https://api.verifik.co/v2/document-validations
A Document Validation is an instance within Verifik's system that allows you to create and manage document verification records. This endpoint creates a new document validation record with the specified configuration and settings.
Headers
Content-Type
application/json
Authorization
Bearer <token>
Body
documentType
string
The type of document being validated (e.g., "Passport", "ID", "DriverLicense").
documentNumber
string
The document number or identifier associated with the document.
url
string
URL where the document can be accessed or viewed.
type
string
The type of validation process. Can be "validation", "login", "signup", "ocr", or "demo".
redirectUrl
string
URL to redirect after the validation process is complete.
webhookUrl
string
URL for webhook callback notifications after validation.
requires2FA
boolean
Indicates if two-factor authentication is required for this validation.
namesMatch
boolean
For signup type validations, indicates if the names on the document match expected names.
Minimal Body Data
{
"documentType": "Passport",
"documentNumber": "123456789",
"type": "validation"
}
Full Body Data
{
"documentType": "Passport",
"documentNumber": "123456789",
"url": "https://example.com/document",
"type": "signup",
"redirectUrl": "https://example.com/redirect",
"webhookUrl": "https://example.com/webhook",
"requires2FA": false,
"namesMatch": true
}
Request
curl -X POST https://api.verifik.co/v2/document-validations \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"documentType": "Passport",
"documentNumber": "123456789",
"url": "https://example.com/document",
"type": "signup",
"redirectUrl": "https://example.com/redirect",
"webhookUrl": "https://example.com/webhook",
"requires2FA": false,
"namesMatch": true
}'
Response
The response will contain information about the new Document Validation
instance. Important fields include the unique identifier _id
, the status
of the validation process, and the configured settings.
{
"data": {
"_id": "507f1f77bcf86cd799439011",
"documentType": "Passport",
"documentNumber": "123456789",
"url": "https://example.com/document",
"type": "signup",
"redirectUrl": "https://example.com/redirect",
"webhookUrl": "https://example.com/webhook",
"requires2FA": false,
"namesMatch": true,
"status": "ASSESSING",
"validationMethod": "MANUAL",
"inputMethod": "NOT_SET",
"imageValidated": false,
"createdAt": "2025-01-01T00:00:00.000Z",
"updatedAt": "2025-01-01T00:00:00.000Z"
}
}
Key Differences from App Registration Endpoint:
This endpoint creates a standalone document validation record
No automatic image processing or OCR analysis
Requires manual configuration of document details
Used for administrative or programmatic document validation creation
Does not automatically link to an app registration process
Note: This endpoint is different from the /document-validations/app-registration
endpoint, which is specifically designed for processing documents during the app registration flow with automatic image analysis and OCR processing.
Last updated
Was this helpful?