DIN Verification API for Corporate Due Diligence
Validate Director Identification Numbers (DIN) against MCA records — verify director identity, designation, and associated companies for KYB and compliance workflows.
Starts at ₹2.04 per verification · excl. GSTView Pricing
Overview
The DIN Verification API enables businesses to validate Director Identification Numbers against Ministry of Corporate Affairs records. Use it for corporate due diligence, KYB workflows, and director background checks.
What Can You Verify With DIN Verification API?
Key details returned across all DIN Verification API endpoints, ready to power your KYC and onboarding workflows.
Director Identification Number (DIN)
The DIN submitted in the request, echoed back for confirmation.
Director's Name
Full legal name of the director as registered with MCA.
DIN Status
Current status of the DIN as recorded by MCA — e.g. Active, Deactivated, Surrendered, Disqualified.
Designation
Role or designation of the director as filed with MCA.
Company Name
Name of the company with which the director is associated, as recorded in MCA records.
DIN Verification API Flow – Sample Request and Response
Send simple inputs. Get rich, verified data in seconds.
Verify Director Identification Numbers (DIN) against MCA records — returns director name, DIN status, designation, and associated company information.
Key Features
Everything you need to integrate and scale
Real-Time DIN Validation
Verify DIN details instantly against Ministry of Corporate Affairs records.
Director Identity
Confirm director name, designation, and DIN status for due diligence.
Corporate Linkage
Identify companies associated with a director for cross-referencing.
Automation Friendly
Integrate into KYB pipelines, compliance checks, and onboarding workflows.
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 DINs in production.
Frequently Asked Questions
What input is required?+
Only the Director Identification Number (DIN) is required.
What details are returned?+
The API returns director name, DIN status, designation, and associated company information from MCA records.
How is DIN different from CIN?+
DIN identifies individual directors, while CIN identifies companies. Use DIN Verification for director-level checks and CIN Verification for company-level checks.
Can I verify multiple directors at once?+
Each API call verifies one DIN. For bulk verification, you can make parallel API calls.
How do I get started?+
Sign up at ekostore.app/eps, verify your identity with your PAN and address details, load your wallet to test the verification APIs live, then integrate and go live.
What is EPS?+
EPS (Eko Platform Services) is the technology arm of Eko, providing the developer tools, AI tools, and APIs that power modern fintech integration.
What are the different ways to integrate with Eko EPS?+
Integrate in whichever way suits your stack: call the REST APIs directly, use our official SDKs (JavaScript and PHP) to skip request-signing boilerplate, or let an AI coding agent build the integration using our MCP server and skills. See the Developers and AI sections for each path.
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.
Is there a sandbox environment for testing?+
Yes. A full sandbox environment is available immediately on signup. You can test your integration end-to-end before going live — no commitment required.
What are the sandbox and production base URLs?+
Sandbox and production share the same paths and differ only by base URL: use https://staging.eko.in/ekoapi/v3 for UAT / Sandbox, and https://api.eko.in/ekoicici/v3 for Production. A common cause of failures is calling the sandbox/staging 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, share your static public IP with us so we can whitelist it.
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 — contact our team for detailed rates.
Recommended Solution Packs
Pre-bundled API stacks that include DIN 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 DIN Verification API Access
Get started in 10 minutes