KwikID DocumentationVerify Passport
Verify passport details with number, file number, DOB, date of issue, and consent. Server-side POST with Bearer auth.
API reference
JWT Bearer token authentication. Obtain a token from the KwikID dashboard.
In: header
Passport date of issue in YYYY-MM-DD format
Passport file number assigned by the issuing authority
Applicant's date of birth in YYYY-MM-DD format
Passport number printed on the document
Applicant consent flag; use Y to indicate explicit consent
Response Body
curl -X POST "https://__mock__/verification/v2/passport/verify" \ -H "Content-Type: application/json" \ -d '{ "doi": "2020-01-15", "file_no": "XX0000000000000", "dob": "1990-06-01", "passport_no": "XX1234567", "consent": "Y" }'{
"application_date": "15/01/2020",
"date_of_birth": {
"date_of_birth_from_source": "01/06/1990",
"date_of_birth_match": true
},
"name": "JANE DOE",
"passport_number": {
"passport_number_from_source": "XX1234567",
"passport_number_match": true
},
"type_of_application": "Normal",
"credits_consumed": 1
}{
"detail": {},
"message": "Passport verification failed - Action Errors: ['The status of the entered File Number is not available in the system.']"
}{
"detail": {},
"message": "string"
}{
"error": "string"
}Overview
Call POST /verification/v2/passport/verify from your backend with Authorization: Bearer <token> and JSON passport_no, file_no, dob, doi (date of issue, YYYY-MM-DD), and consent (Y). The 200 response includes match-style fields such as name, passport_number, and nested date_of_birth verification as in OpenAPI.
Key features
- Field-level checks for DOB and passport metadata.
- Consent flag aligns with regulated KYC workflows.
Implementation
Step 1: Call from your backend
POST /verification/v2/passport/verify HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>
Content-Type: application/json
{
"passport_no": "X1234567",
"file_no": "ABCDE1234567890",
"dob": "1990-06-01",
"doi": "2020-01-15",
"consent": "Y"
}Step 2: Use the response
Read boolean and string fields to decide pass or manual review.
Error handling
| HTTP status | When |
|---|---|
| 400 | Validation error. |
| 401 | Invalid token. |
Benefits
- Supports passport-first onboarding without manual data re-entry.