Browse documentation
Identity & KYC Verification APIs

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

POSThttps://verification.techinnoverz.com/api/v1/identity-kyc/passport

Validate a passport file number and date of birth. This call is billed when it returns a successful result.

Request body

fileNumberstringrequired

The passport application file number, 6 to 30 letters and digits, as on the application receipt.

dateOfBirthstringrequired

The passport holder's date of birth, YYYY-MM-DD.

consentstringrequired

Must be "Y". Records that the end customer consented to this check; logged against the transaction.

referenceIdstringoptional

Your 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"
}'

200 response — status "found"

Response
{
  "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

applicationStatusstringoptional

ISSUED 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.

fileNumberstringoptional

The passport application file number, as the source holds it (it may be partly masked).

dateOfBirthstringoptional

The holder's date of birth, YYYY-MM-DD.

passportNumberstringoptional

The passport number, masked by the source. null unless the passport is issued.

givenNamestringoptional

Given name on the passport application.

surnamestringoptional

Surname on the passport application. null when the source does not give one.

applicationTypestringoptional

Normal or Tatkal.

applicationDatestringoptional

The date the application was made, YYYY-MM-DD.

dateOfDispatchstringoptional

The 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_INPUT

A field is missing or malformed. The details list each problem. Not charged.

401 INVALID_KEY

The key is missing, revoked, or not a key we issued.

402 WALLET_EMPTY

Your available balance is below the price of this call. Top up and retry. Not charged.

403 PRODUCTION_NOT_ENABLED

A 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_ENABLED

A test key was used before test (UAT) access was enabled for your account. Ask us to enable it.

403 API_NOT_ENABLED

This check is switched off for your account, or is not available for live use yet.

403 IP_NOT_ALLOWED

The key is restricted to certain IP addresses and this call came from another.

403 ACCOUNT_SUSPENDED

The account is suspended. Contact support.

404 NO_DATA

A valid request, but no record was found. Not charged.

404 ROUTE_NOT_FOUND

There is no endpoint at that path.

405 METHOD_NOT_ALLOWED

Use the method shown in the Allow header.

409 IDEMPOTENCY_IN_PROGRESS

A call with the same Idempotency-Key is still being processed. Retry after the delay in Retry-After.

413 PAYLOAD_TOO_LARGE

The request body is too large. Not charged.

415 UNSUPPORTED_MEDIA_TYPE

Send the request with Content-Type: application/json.

422 IDEMPOTENCY_KEY_REUSED

This Idempotency-Key was already used with a different request body. Use a new key for a new request.

429 RATE_LIMITED

Too many requests or too many at once. Wait for the Retry-After delay.

500 INTERNAL_ERROR

Something went wrong on our side. Not charged. Quote the txnId if you contact support.

502 SOURCE_ERROR

The data source returned an error. Not charged.

503 SOURCE_DOWN

The data source is unavailable right now. Not charged. Retry after the delay in Retry-After.

504 SOURCE_TIMEOUT

The data source did not answer in time. Not charged.

Error response
{
  "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

All API documentation · OpenAPI specification · Docs as plain text