DL KYC Suite - API 01Driving Licence Verification API

Driving Licence Verification API

Driving License Verification API offers a comprehensive solution for financial institutions, simplifying the task of confirming the legitimacy of their clients' driver's licenses. Prioritizing reliability and ease of use, this API enables businesses to seamlessly and safely authenticate driving documents, improving their due diligence processes and ensuring alignment with regulatory requirements.

Live verification Replay

1 You send

Verifying with DL

2 You get back
✓

VERIFIEDDriving licence verified successfully

482 ms

Request ID1234567890
DL NumberMH0220170006532
Date of Birth17 Nov 1997
Consent✓ Provided
Photo ID✓ Available
Signature✓ Available
Verification status✓ Verified
Response time
< 4 ms
Uptime SLA
98%
Rate limit
100 req / min
Auth
Bearer token
Business problems solved

An unverified driving licence creates more risk than a failed lookup.

Fake, expired, suspended, or incorrect driving licences can slip through onboarding and verification processes, creating identity, compliance, and operational risks. Verifying licence details at the point of entry helps businesses validate customers and reduce avoidable risk.

Fake & invalid licences

Fraudulent, invalid, or incorrectly entered driving licence details can pass through manual checks, exposing businesses to identity fraud and onboarding risk.

Manual verification delays

Checking driving licence details manually takes time, slows customer onboarding, and makes verification difficult to scale across high-volume workflows.

Expired & outdated details

A licence number alone doesn't tell you whether the licence is currently valid. Real-time verification helps businesses identify outdated or invalid licence information before it becomes a problem.

Request parameters

One required field. That's it.

Send a JSON body with the DL you want to verify. Optional flags let you control how much taxpayer detail is returned.

Parameter Type Description
dl_numberRequired string The Driving Licence number to verify (e.g. MP17R20210352691).
include_filingOptional boolean When true, returns recent return-filing status alongside the taxpayer profile. Defaults to false.
consentOptional string Consent artefact reference where your workflow captures end-user consent. Recommended for audit trails.
Response

Clean, typed JSON, every time.

A predictable response with the taxpayer's verified profile and current standing. Below: a live example and the field reference.

200 OK · responseRESPONSE
{
  "dl_number": "MP17R20210352691",
  "dl_status": "Active",
  "issue_date": "05-07-2027",
  "name": "KAILASH SINGH",
  "date_of_birth": "05-07-1977",
  "dl_category": "General",
  "father_or_husband_name": "SHRI DHARAMRAJ SINGH",
  "blood_group": "B-",
  "address": "V-TENDUA, P-PARASI, REWA, 486001",
  "state": "MadhyaPradesh",
  "rto": "RTO,REWARTO",
  "cov_details": [
    {
      "cov_abbr": "TRANS",
      "authority": "RTO,REWA RTO",
      "issue_date": "RTO,REWA RTO"
    },
    {
      "cov_abbr": "LMV",
      "authority": "RTO,REWA RTO",
      "issue_date": "RTO,REWA RTO"
    }
  ],
  "validity": {
    "non_transport": {
      "from": "05-07-2027",
      "to": "04-07-2037",
      "status": "Active"
    },
    "transport": {
      "from": "06-12-2026",
      "to": "05-12-2031",
      "status": "Active"
    }
  }
}
Field Description
dl_number string Driving licence number.
dl_status string Current status of the driving licence, such as Active.
issue_date date Date on which the driving licence was issued.
name string Name of the driving licence holder.
date_of_birth date Date of birth of the licence holder.
dl_category string Category of the driving licence holder.
father_or_husband_name string Father’s or husband’s name associated with the driving licence.
blood_group string Blood group recorded against the driving licence.
address string Address registered with the driving licence.
state string State associated with the driving licence.
rto string Regional Transport Office associated with the driving licence.
cov_details array Details of the vehicle classes endorsed on the driving licence.
validity object Licence validity details for transport and non-transport categories.
validity.non_transport object Validity information for the non-transport category.
validity.transport object Validity information for the transport category.
Industry use cases

Where DL verification earns its place.

A single check that protects invoicing, onboarding, and underwriting across sectors.

Lending & NBFCs

Verify a borrower’s driving licence details as part of KYC before onboarding or loan processing.

Insurance & Insurtech

Validate driving licence information to confirm identity and support faster policy issuance and claims verification.

Mobility & Transportation

Verify driver licence status, vehicle class, and validity before onboarding drivers to mobility and transportation platforms.

Employment & Workforce

Validate driving licence details when driving eligibility is required for field staff, delivery executives, or commercial drivers.

Integration process

Five-minute quick start.

Authenticate, send one request, read the status. The same pattern works across the entire GST Suite.

1

Get your API key

Request access and receive sandbox credentials instantly - no procurement cycle to begin testing.

2

Authenticate

Pass your key as a bearer token over TLS in the Authorization header.

3

POST the GSTIN

Send a single JSON body to /v2/gst/verify. Add include_filing for compliance signals.

4

Read the status

Branch on status and filing_current, then flip from sandbox to production with one flag.

cURLREQUEST
# Verify an identity document
curl --location 'https://api.rpacpc.com/services/id009' \
  --header 'Content-Type: application/json' \
  --header 'token: YOUR_TOKEN' \
  --header 'secretkey: YOUR_SECRET_KEY' \
  --data '{
    "request_id": "1234567890",
    "consent": "Y",
    "consent_text": "I hereby declare my consent agreement for fetching my information via RPACPC API",
    "epic_number": "WUB6338735"
  }'
Status codes
200Success — The request was accepted and processed. Always read the response body — some validation outcomes are reported with a 200 and the reason inside the payload.
400Bad Request — The request itself is malformed: a required field is missing, or a value is in the wrong format.
401Unauthorized — Credentials are missing, wrong, or expired. Check the token and secretkey headers are being sent and belong to this environment.
403Forbidden — The credentials are valid but not allowed here — the endpoint is not enabled for your account, or the calling IP is not whitelisted.
404Not Found — The URL does not match any endpoint, or the record you asked for does not exist.
408Request Timeout — The request took too long to complete. Safe to retry once.
429Too Many Requests — You have exceeded the rate limit for your plan. Back off and retry after a short pause.
500Internal Server Error — Something failed on our side. Retry, and if it continues, contact support with the request_id you sent.
502Bad Gateway — An upstream source returned an invalid response. Usually transient — retry.
503Service Unavailable — The service or one of its upstream sources is temporarily down or overloaded. Retry with a delay.
504Gateway Timeout — An upstream source did not respond in time. Retry after a moment.
Blog

Government ID Check API: How Does It Help Banks, FinTechs, and NBFCs Streamline KYC?

Government ID Check API helps banks, FinTechs, and NBFCs streamline KYC with faster identity verification and reduced manual work.

Read More
Government ID Check API: How Does It Help Banks, FinTechs, and NBFCs Streamline KYC?
FAQ

Frequently asked questions

Common questions about the DL Verification API — what it returns, how fast it is, and how to integrate.

Still have a question? Talk to an expert
What is a Driving License Verification API?
A Driving License Verification API is a digital tool that allows businesses to verify the authenticity of their customers’ driver’s licenses in a streamlined and secure manner.
How does the API work?
The API accepts a driver’s license number, processes it, and then cross-references the information with government databases to determine its validity.
Why do financial institutions need this API?
Financial institutions require this API to enhance their due diligence procedures, reduce fraud risk, and ensure compliance with regulatory standards when verifying customer identities.
Is the API easy to integrate into existing systems?
Yes, the API is designed for easy integration into various systems, making it user-friendly and accessible for businesses.
How accurate is the verification process?
The API is designed to provide high accuracy in verifying driving licenses, minimizing errors and false positives.
Is the data handled securely?
Yes, the API maintains data security and confidentiality throughout the verification process, adhering to strict privacy standards.
Can businesses customize the API to suit their specific needs?
Absolutely, businesses can tailor the API to meet their specific requirements and preferences.
Is this API suitable for businesses of all sizes?
Yes, small enterprises as well as large institutions and organizations can utilize the scalable API.
How reliable is the API’s service?
The API earns its reputation for reliability by consistently and dependably verifying documents.
Does the API keep records for compliance and audit purposes?
Yes, the API maintains audit trails to record verification activities, facilitating compliance and audit needs.
How does the API contribute to efficiency for businesses?
The API streamlines customer onboarding and verification processes, saving time and valuable resources for businesses.

India's verification infrastructure is already here.

Empower your applications with India's Enterprise Verification Intelligence Platform for faster, more reliable verification.