Passport Verification API
Validate a passport file number and date of birth and get the holder's name, passport number and application dates.
What it verifies
Validates a passport application file number together with the holder's date of birth. When they match you get the holder's name, the application type and date and, once issued, the masked passport number and dispatch date. An application that is still under review or was rejected is returned too, with its status. A file number that is invalid, or has no record with that date of birth, is reported as no data; a file number of a passport issued outside India cannot be validated and is rejected as invalid input.
Who uses it
- Travel, immigration and visa-services platforms confirming a traveller's passport
- Lenders and employers accepting a passport as identity proof
- Background-verification firms validating a passport against its application record
Request and response
https://verification.techinnoverz.com/api/v1/identity-kyc/passportValidate a passport file number and date of birth. This call is billed when it returns a successful result.
Request body
fileNumberstringrequiredThe passport application file number, 6 to 30 letters and digits, as on the application receipt.
dateOfBirthstringrequiredThe passport holder's date of birth, YYYY-MM-DD.
consentstringrequiredMust be "Y". Records that the end customer consented to this check; logged against the transaction.
referenceIdstringoptionalYour own id, echoed back in the response for reconciliation.
Example requests
curl -X POST "https://verification.techinnoverz.com/api/v1/identity-kyc/passport" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"fileNumber": "GZ1075123456789",
"dateOfBirth": "1993-06-06",
"consent": "Y",
"referenceId": "app_20915"
}'const res = await fetch("https://verification.techinnoverz.com/api/v1/identity-kyc/passport", {
method: "POST",
headers: {
"x-api-key": "YOUR_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
"fileNumber": "GZ1075123456789",
"dateOfBirth": "1993-06-06",
"consent": "Y",
"referenceId": "app_20915"
}),
});
const result = await res.json();import requests
res = requests.post(
"https://verification.techinnoverz.com/api/v1/identity-kyc/passport",
headers={"x-api-key": "YOUR_API_KEY"},
json={
"fileNumber": "GZ1075123456789",
"dateOfBirth": "1993-06-06",
"consent": "Y",
"referenceId": "app_20915",
},
timeout=15,
)
result = res.json()200 response — status "found"
{
"status": "found",
"data": {
"applicationStatus": "ISSUED",
"fileNumber": "GZ1075123456789",
"dateOfBirth": "1993-06-06",
"passportNumber": "P1234567",
"givenName": "Asha",
"surname": "Sample",
"applicationType": "Normal",
"applicationDate": "2016-09-09",
"dateOfDispatch": "2016-10-31"
},
"source": "provider",
"dataAsOf": "2026-11-03T09:30:00.000Z",
"referenceId": "app_20915",
"billing": {
"charged": true,
"walletBalance": "12450.00"
},
"txnId": "txn_8c31ba90",
"livemode": true
}Fields returned in data
applicationStatusstringoptionalISSUED when the passport has been issued, UNDER_REVIEW when the application is still being processed (a passport number may follow on a later check) and REJECTED when the application was rejected.
fileNumberstringoptionalThe passport application file number, as the source holds it (it may be partly masked).
dateOfBirthstringoptionalThe holder's date of birth, YYYY-MM-DD.
passportNumberstringoptionalThe passport number, masked by the source. null unless the passport is issued.
givenNamestringoptionalGiven name on the passport application.
surnamestringoptionalSurname on the passport application. null when the source does not give one.
applicationTypestringoptionalNormal or Tatkal.
applicationDatestringoptionalThe date the application was made, YYYY-MM-DD.
dateOfDispatchstringoptionalThe date the passport was dispatched, YYYY-MM-DD. null unless the passport is issued.
Error codes
Errors return a non-200 HTTP status and the same envelope, so your retry logic and your reconciliation agree.
400 INVALID_INPUTA field is missing or malformed. The details list each problem. Not charged.
401 INVALID_KEYThe key is missing, revoked, or not a key we issued.
402 WALLET_EMPTYYour available balance is below the price of this call. Top up and retry. Not charged.
403 PRODUCTION_NOT_ENABLEDA live key was used before live access was enabled for your account. Use a test key, or ask us to enable live access.
403 TEST_NOT_ENABLEDA test key was used before test (UAT) access was enabled for your account. Ask us to enable it.
403 API_NOT_ENABLEDThis check is switched off for your account, or is not available for live use yet.
403 IP_NOT_ALLOWEDThe key is restricted to certain IP addresses and this call came from another.
403 ACCOUNT_SUSPENDEDThe account is suspended. Contact support.
404 NO_DATAA valid request, but no record was found. Not charged.
404 ROUTE_NOT_FOUNDThere is no endpoint at that path.
405 METHOD_NOT_ALLOWEDUse the method shown in the Allow header.
409 IDEMPOTENCY_IN_PROGRESSA call with the same Idempotency-Key is still being processed. Retry after the delay in Retry-After.
413 PAYLOAD_TOO_LARGEThe request body is too large. Not charged.
415 UNSUPPORTED_MEDIA_TYPESend the request with Content-Type: application/json.
422 IDEMPOTENCY_KEY_REUSEDThis Idempotency-Key was already used with a different request body. Use a new key for a new request.
429 RATE_LIMITEDToo many requests or too many at once. Wait for the Retry-After delay.
500 INTERNAL_ERRORSomething went wrong on our side. Not charged. Quote the txnId if you contact support.
502 SOURCE_ERRORThe data source returned an error. Not charged.
503 SOURCE_DOWNThe data source is unavailable right now. Not charged. Retry after the delay in Retry-After.
504 SOURCE_TIMEOUTThe data source did not answer in time. Not charged.
{
"status": "error",
"error": {
"code": "NO_DATA",
"message": "No record found for the given input. Not charged."
},
"billing": {
"charged": false
},
"txnId": "txn_8c31ba91",
"livemode": true
}Billing
You are charged only on successful hits. Failed, no-data and error calls are free.
Every response carries billing.charged and your remaining billing.walletBalance. Per-hit pricing is set on your rate card; book a demo to get yours.
Related checks
- PAN Verification API — Verify PAN card details and status against Income Tax Department records.
- PAN Advanced Verification API — Verify a PAN and also get its holder type and whether it is linked to Aadhaar.
- PAN Plus Verification API — Everything in PAN Advanced plus the PAN status, allotment date, authorised signatory of a company PAN and whether the holder is a sole proprietor, director or salaried.
- ITR Verification API — Check the income tax return filing history of a PAN: the acknowledgement number for each recent assessment year.
- Voter ID Verification API — Verify EPIC (Voter ID) details against Election Commission of India records.
- Driving Licence Verification API — Verify driving licence number, validity and vehicle class against Parivahan records.
- Driving Licence Advanced Verification API — Verify a driving licence and also get split addresses, vehicle category dates, blood group and endorsement details.
- DigiLocker Verification API — Start a DigiLocker consent flow, then fetch the person's verified documents and demographics once they approve.
- Face Liveness Verification API — Check whether a selfie shows a live person, with quality signals such as blur, mask, alignment and occlusion.
- Face Match Verification API — Compare a live selfie with a face on an identity document and return whether they match, with confidence and quality signals.
All API documentation · OpenAPI specification · Docs as plain text
