---
type: "product"
title: "Driving License Verification API India | Real-Time DL Validation"
description: "Integrate Driving License Verification API to validate driving license details instantly for KYC, onboarding, and compliance checks."
category: "verification"
canonical: "https://eps.eko.in/products/dl-verification-api"
---


> **Canonical URL:** https://eps.eko.in/products/dl-verification-api
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# Driving License Verification API for Driver Onboarding & KYC

Verify driving license details in real time to strengthen KYC and reduce identity fraud.

_Real-time DL validation_

To get started, fill the form at https://eps.eko.in/signup (with your name, mobile number and email) or call us at +919513181707

## Overview

The Driving License Verification API enables businesses to validate driving license details instantly as part of identity verification and onboarding workflows. It helps confirm user identity, reduce impersonation risk, and meet compliance requirements.

## Features

- Real-Time DL Validation: Verify driving license details instantly with structured verification responses.
- Identity Confirmation: Use DL data as a trusted identity signal during onboarding.
- Automation Ready: Seamlessly integrates into digital KYC and onboarding pipelines.
- High-Volume Support: Built to handle large verification volumes reliably.

## Who Should Use This

- Fintech and lending platforms
- Mobility and logistics companies
- Marketplaces onboarding drivers or agents
- Enterprises with identity verification needs

## Use Cases

- Customer identity verification
- KYC onboarding workflows
- Driver or delivery partner onboarding
- Compliance and due diligence checks

## What Can You Verify With Driving Licence Verification API?

- **Driving License Number** — The driving license number that was verified.
- **Date of Birth** — Date of birth of the DL holder as returned by the authority.
- **Status** — Overall status of the driving license (e.g. Active, Suspended, Expired).
- **Name** — Full name of the driving license holder.
- **Father Or Husband Name** — Father's or husband's name as recorded on the DL.
- **Date Of Issue** — Date the driving license was originally issued (YYYY-MM-DD).
- **Address List** — List of addresses associated with the DL holder.
- **Complete Address** — Full address string as recorded on the DL.
- **Cov Details** — Class of Vehicle (COV) entitlement records — each entry lists a vehicle class and associated validity.
- **Cov** — Vehicle class code, e.g. LMV, MCWG, TRANS.
- **Dl Validity** — Validity windows for transport and non-transport license categories.
- **Non Transport** — Validity period for non-transport (personal) vehicle authorisation.
- **From** — Non-transport validity start date (YYYY-MM-DD).
- **To** — Non-transport validity end date (YYYY-MM-DD).
- **Transport** — Validity period for transport (commercial) vehicle authorisation.
- **Badge Details** — Badge/transport endorsement records, each describing a permitted vehicle class group.
- **Badge No** — Badge number assigned by the transport authority.
- **Class Of Vehicle** — List of vehicle classes covered under this badge (e.g. LMV, MCWG, TRANS).

## API Preview — Driving License Verification

`POST /tools/kyc/driving-license`

### Example inputs

| Field | Value |
| --- | --- |
| Dl Number | KA0120198900984 |
| Dob | 1994-08-05 |

### Example outputs

| Field | Value |
| --- | --- |
| Driving License Number | KA0120198900984 |
| Date of Birth | 1994-08-05 |
| Status | Active |
| Name | Rajesh Kumar |
| Father Or Husband Name | Suresh Kumar |
| Date Of Issue | 2019-03-15 |
| Status | Active |
| Complete Address | 123, Andheri West, Mumbai, Maharashtra - 400053 |
| Cov | LMV |
| From | 2019-03-15 |
| To | 2039-03-14 |
| From | 2019-03-15 |
| To | 2024-03-14 |
| Badge No | MH-BADGE-001 |
| Class Of Vehicle | ["LMV","MCWG"] |

## Integration Steps

1. **[Sign Up](/console)** — 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](/ai)** — Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
5. **Go Live** — Start verifying driving licenses in production.

## FAQs

### DL Verification vs RC Verification?
Driving License Verification validates the person’s license details, such as holder name, DOB, validity, address, and vehicle class eligibility. Vehicle RC Verification validates vehicle registration details, ownership, insurance, and registration status. For complete driver and vehicle onboarding, combine DL Verification with RC Verification.

### How fast is DL verification?
Verification is real-time with instant structured responses for driving license details.

### Can I use it for driver onboarding?
Yes, it's ideal for onboarding drivers, delivery partners, and agents requiring identity confirmation.

### How do I get started?
Four steps: **sign up** at the [developer console page](/console), 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 **Node.js, Python, PHP, Go or Java SDKs** to skip request-signing boilerplate.
- Let an **AI coding agent** build it via our [MCP server and agent skills](/ai#install).

For multi-step flows (onboard a sender, *then* transfer) start from a [transaction-flow recipe](/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](/docs/how-auth-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.

### Why does my API call return 401 Unauthorized?
Authentication failed. For the known causes, the response body's `status` names the check that failed:

- `2483` — The developer_key is wrong.
- `2484` — The secret-key (signature) is wrong.
- `2485` — The secret-key-timestamp is more than 2 minutes older or newer than the server clock, or was reused from an earlier request.
- `2486` — The secret-key-timestamp is not in milliseconds (13 digits) — often seconds (10 digits).
- `2487` — The secret-key or secret-key-timestamp header is missing.

If your signature checks out in the [secret-key playground](/docs/how-auth-works#try-it-secret-key-playground) and you still get a `401`, make sure the base URL matches your keys (UAT vs production) and, in production, that your server's IP is whitelisted.

### 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](/ai#artifacts) (`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?
It's optional. **IP whitelisting** is available for **production** access as an extra layer of security — share your **static public (server) IP** with us and we'll 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](/ai#install), or start from a [ready-made prompt](/ai#quick-start).

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](/pricing) for indicative rates, or contact our team for a custom quote.

## API Endpoints

- [Driving License Verification](https://eps.eko.in/docs/driving-license.md) (POST)

## API Documentation

- [Full developer docs](https://eps.eko.in/docs/driving-license)

## Related Products

- [Mobile/OTP Verification](https://eps.eko.in/products/mobile-otp-verification-api): Send, verify & validate mobile OTPs with a signed proof token ([markdown](https://eps.eko.in/products/mobile-otp-verification-api.md))
- [PAN Verification](https://eps.eko.in/products/pan-verification-api): Full PAN identity fetch in <2 seconds ([markdown](https://eps.eko.in/products/pan-verification-api.md))
- [Bank Account Verification](https://eps.eko.in/products/bank-verification-api): Penny-drop bank account validation ([markdown](https://eps.eko.in/products/bank-verification-api.md))
- [GST Verification](https://eps.eko.in/products/gst-verification-api): GSTIN lookup & filing status ([markdown](https://eps.eko.in/products/gst-verification-api.md))
- [DigiLocker Integration](https://eps.eko.in/products/digilocker-api): Fetch notarised docs — Aadhaar, DL, marksheets, etc ([markdown](https://eps.eko.in/products/digilocker-api.md))

- [Site index](https://eps.eko.in/index.md): Full list of API products, industries, and solution packs