Passport Verification API for Indian Passport File Number Checks
Verify Indian passport application details using passport file number and date of birth. Retrieve verification status, holder name, date of birth, application type, and application received date for KYC, employee BGV, travel, and compliance workflows.
Starts at ₹1.80 per verification · excl. GSTView Pricing
Overview
The Passport Verification API enables businesses to validate passport holder details using passport file number and date of birth.
What Can You Verify With Passport Verification API?
Key details returned across all Passport Verification API endpoints, ready to power your KYC and onboarding workflows.
File Number
Unique alphanumeric code identifying the passport application, echoed back from the source.
Name
Full name of the passport holder as recorded in the government source.
Date of Birth
Date of birth of the passport holder (YYYY-MM-DD) as registered in the passport application.
Application Type
Type of passport application (e.g. Normal, Tatkal). Indicates the application category used when the passport was applied for.
Application Received Date
Date on which the passport application was received by the issuing authority (YYYY-MM-DD format).
Passport Verification API Flow – Sample Request and Response
Send simple inputs. Get rich, verified data in seconds.
Verify Indian passport application details using passport file number and date of birth.
Key Features
Everything you need to integrate and scale
Real-Time Passport Validation
Verify Indian passport file number and holder details with instant structured responses.
Identity Confirmation
Cross-check holder name and date of birth against passport records.
Application Status
Returns application type and received date for processing verification.
Automation Friendly
Easily integrate into digital onboarding, KYC, and compliance pipelines.
Who Should Use This API?
Primary Use Cases
How to Integrate
Get started in minutes with our simple integration process
- 1
Sign Up
Sign up in minutes with your mobile number (OTP verify).
- 2
Verify Identity
Complete your basic KYC with PAN and address details to verify your identity.
- 3
Test APIs Live
Load funds into your wallet and test the verification APIs live — evaluate before you integrate.
- 4
Integrate with AI
Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
- 5
Go Live
Start verifying passports in production.
Frequently Asked Questions
Is this passport number verification or file number verification?+
This API verifies Indian passport details using passport file number and date of birth. It is not a passport-number-only verification flow.
What inputs are required?+
The required inputs are passport file number and date of birth. A unique verification ID is also used for request tracking. Name may be used depending on the verification flow.
Does this API support foreign passports?+
No. This API supports Indian passport verification only.
What details are returned?+
The API can return verification status, passport file number, holder name, date of birth, application type, and the application received date.
Does it return passport issue date or expiry date?+
No, not as part of the standard source response shown in the current API documentation. Do not rely on issue date or expiry date unless separately enabled in your Eko API response.
Does it verify scanned passport images?+
No. This is not an OCR or MRZ scan-verification API. It verifies passport details using structured input fields.
What happens if the details are invalid?+
The API returns an invalid status. Your workflow should ask the user to verify the file number, date of birth, and name before retrying.
How fast is passport verification?+
Verification is real-time with sub-second response times.
How do I get started?+
Four steps: sign up at the developer console page, verify your identity with PAN and address details, load your wallet to test the APIs live, then integrate and go live. Sandbox credentials are issued immediately — you can call your first endpoint before any paperwork clears.
What is EPS?+
EPS (Eko Platform Services) is the technology arm of Eko — the developer tools, AI tooling and APIs that power modern fintech integration, from money transfer and AePS to identity verification.
What are the different ways to integrate with Eko EPS?+
Three paths, pick whichever suits your stack:
- Call the REST APIs directly.
- Use our official JavaScript / PHP SDKs to skip request-signing boilerplate.
- Let an AI coding agent build it via our MCP server and agent skills.
For multi-step flows (onboard a sender, then transfer) start from a transaction-flow recipe rather than wiring single endpoints together yourself.
How does API authentication work?+
Each request carries your static developer_key header plus a per-request secret-key header — an HMAC-SHA256 signature of the current timestamp, keyed by your access key. The access key itself is never sent over the wire. You receive UAT keys on signup and production keys after KYC.
The How Authentication Works guide has the full signing recipe in five languages plus an in-browser playground that generates and verifies a real secret-key against your own access key.
Is there a sandbox environment for testing?+
Yes. A full sandbox is available immediately on signup — test your integration end-to-end before going live, no commitment required. For offline work you can also run our mock server (npx -y @ekoindia/eps-mock-server) and get canned responses with no network calls at all.
What are the sandbox and production base URLs?+
Sandbox and production share the same paths and differ only by base URL:
- UAT / Sandbox —
https://staging.eko.in/ekoapi/v3 - Production —
https://api.eko.in/ekoicici/v3
A common cause of failures is calling the sandbox URL with live credentials, or vice-versa — make sure the base URL matches the keys you are using.
Do I need to whitelist my server IP?+
Production API access may require your static public (server) IP to be whitelisted. If your calls work from Postman but fail or time out from your own server, that is almost always the cause — share your static public IP with us so we can whitelist it.
Can an AI coding agent build the integration for me?+
Yes — that is the fastest path. Point your agent (Claude Code, Codex, Cursor, Copilot, …) at our MCP server and it can look up any endpoint, generate correctly-signed requests, and scaffold the integration in your own stack. Install it in one step from the AI hub, or start from a ready-made prompt.
We also publish an OpenAPI 3.1 spec, a Postman collection and per-agent context packs (AGENTS.md, CLAUDE.md, .cursorrules) so an agent has the ground truth instead of guessing.
What response times can I expect?+
Most verification APIs return in real time with sub-second responses, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.
Can the API handle high volumes?+
Yes. The API is designed to handle large-scale volumes reliably without performance degradation.
How is API usage billed?+
Usage is billed per successful API call with no minimum commitment. Volume-based pricing tiers are available — see the pricing calculator for indicative rates, or contact our team for a custom quote.
Recommended Solution Packs
Pre-bundled API stacks that include Passport Verification API, designed for common industry workflows.
Get API Access
Sign up now and start integrating in minutes. Our team will help you go live quickly.
- Sandbox access in minutes
- Dedicated integration support
- Comprehensive documentation
- Reliable, high-volume workflows
Get Passport Verification API Access
Get started in 10 minutes