POSTPassport Application Validation

Validate Indian passport application details using passport file number and date of birth.

POST/tools/kyc/passport

The Passport Application Validation API enables businesses to validate passport holder details using passport file number and date of birth. Returns holder name, DOB, application type, and application received date — suitable for KYC, employee background verification, travel compliance, and fintech onboarding workflows. Supports Indian passports only; not an OCR or MRZ scan API.

Request

Body parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`client_ref_id`	string	optional	Unique reference ID per API call, generated by your system (max 20 characters).e.g. 2026010100123456789
`file_number`	string	required	Unique alphanumeric code that identifies an individual's passport application (passport file number).e.g. J8369854
`dob`	string	required	Date of birth of the passport holder in YYYY-MM-DD format.e.g. 1994-08-29
`name`	string	optional	Name of the passport holder. Optional — used for cross-checking in certain verification flows.e.g. Rajesh Kumar

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

client_ref_idstringoptional

Unique reference ID per API call, generated by your system (max 20 characters).

example: 2026010100123456789

file_numberstringRequired

Unique alphanumeric code that identifies an individual's passport application (passport file number).

example: J8369854

dobstringRequired

Date of birth of the passport holder in YYYY-MM-DD format.

example: 1994-08-29

namestringoptional

Name of the passport holder. Optional — used for cross-checking in certain verification flows.

example: Rajesh Kumar

These headers authenticate and sign every request. See How Auth Works for details.

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Responses

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- file_numberstring
  Unique alphanumeric code identifying the passport application, echoed back from the source.
- namestring
  Full name of the passport holder as recorded in the government source.
- dobstring
  Date of birth of the passport holder (YYYY-MM-DD) as registered in the passport application.
- application_typestring
  Type of passport application (e.g. Normal, Tatkal). Indicates the application category used when the passport was applied for.
- application_received_datestring
  Date on which the passport application was received by the issuing authority (YYYY-MM-DD format).

POSTPassport Application Validation

Request

Body parameters

Responses

Next steps

Related