Driving License Verification API
Check a submitted driving license number against available license records, and use the holder, validity and vehicle-class details in your own driver onboarding or KYC flow.
Overview
A driving license is issued by a state transport office. It is one of the few documents that records both who a person is and what they are permitted to drive. If you put people behind the wheel, or accept a license as an identity document, the printed card is not enough. You need to know that the license exists, that it is still valid, and that it covers the right vehicle class. The Driving License Verification API takes the license number and the holder's date of birth and returns the available record in structured form. It can carry holder details, the issuing authority, validity dates, covered vehicle classes and current standing. Available fields vary by data source and by the individual license record. Basic and Advanced coverage are available, and your service contract decides what the response can contain. Make every request with the holder's consent and for an authorized business purpose.
- Category
- KYC Services
- Coverage
- India. What is available depends on the issuing state record and your service contract.
- Input
- Driving license number, usually paired with the holder's date of birth
- Output
- Structured holder, validity, vehicle-class and status details, where the record carries them
- Typical users
- Fleet and logistics operators, mobility platforms, insurers, lenders, staffing platforms, rental businesses
- Coverage note
- India. Available fields vary by data source, by the individual license record and by your service contract.
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Endpoint URL and method
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Authentication
Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Request parameters
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused. | 8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$ |
Body
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
input | object | Required | The details to check. | — |
input. | string | Required | — | Matches ^[A-Z0-9]{5,20}$ |
input. | string | Required | — | Matches ^\d{4}-\d{2}-\d{2}$ |
input. | string | Optional | OPTIONAL (Release 1.1): a name to compare with the record's; the answer's nameMatchScore is the comparison. | Matches ^(?=.*[A-Za-z])[A-Za-z .'-]+$. 1 to 120 characters |
options | object | Optional | Settings for this call. | — |
options. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
options. | object | Optional | The person's consent to this check. | — |
options. | boolean | Required | Send true once the person has agreed to the check. | Always true |
options. | string (date-time) | Required | When the person gave consent. | — |
options. | string | Required | What the check is for, for example kyc. | 1 to 64 characters |
Request samples
cURL
curl -X POST https://gateway.staging.finsour.io/v1/identity/driving-licence \
-H "X-Api-Key: $FINSOUR_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"input": {
"licenceNumber": "<licenceNumber>",
"dateOfBirth": "<dateOfBirth>"
}
}'Node.js
const response = await fetch("https://gateway.staging.finsour.io/v1/identity/driving-licence", {
method: "POST",
headers: {
"X-Api-Key": process.env.FINSOUR_API_KEY,
"Idempotency-Key": crypto.randomUUID(),
"Content-Type": "application/json",
},
body: JSON.stringify({
"input": {
"licenceNumber": "<licenceNumber>",
"dateOfBirth": "<dateOfBirth>"
}
}),
});
console.log(response.status, await response.json());Python
import os
import uuid
import requests
response = requests.post(
"https://gateway.staging.finsour.io/v1/identity/driving-licence",
headers={
"X-Api-Key": os.environ["FINSOUR_API_KEY"],
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"input": {
"licenceNumber": "<licenceNumber>",
"dateOfBirth": "<dateOfBirth>",
},
},
timeout=30,
)
print(response.status_code, response.json())Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Response schema
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The result of the check. | — |
data. | boolean | Always | — | — |
data. | string | Always | — | Matches ^[A-Z0-9]{5,20}$ |
data. | string | Sometimes | The licence number in its display form — all but the last four characters X — from FinSour-Version 2026-11-01 (absent before it). Beside the full licenceNumber for one release; the full field is removed in the next version. | Matches ^(?:X{1,16}[A-Z0-9]{4}|[A-Z]{3}X{5}[0-9A-Z]{2})$ |
data. | object or any or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | array of objects | Always | The vehicle classes the licence grants — empty rather than absent when the record lists none. | — |
data. | string or null | Always | The class-of-vehicle code (for example LMV, MCWG). | — |
data. | string or null | Always | — | — |
data. | string or any or null | Always | — | — |
data. | string or any or null | Always | — | — |
data. | string or any or null | Always | The day the class stops being valid, when the record gives one. | — |
data. | number or null | Always | How closely nameToMatch matches the name the record holds, 0 to 100, to two decimals; null when no name was sent. | Minimum 0. Maximum 100 |
data. | object | Always | — | — |
data. | string | Always | When the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset. | Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$ |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Error codes
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The upstream source did not respond in time. | Safe to retry |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Rate limits
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Use cases
- Logistics and fleet: check a driver's license class before assigning a vehicle
- Ride-hailing and delivery: verify driver-partners at onboarding and at renewal
- Staffing and gig platforms: evidence a placed driver held a valid license for the assignment
- Insurance: check license validity and class in motor underwriting and claim assessment
- Lending and NBFCs: verify identity and driving eligibility in commercial-vehicle finance
- Rental and self-drive: check a renter's license before you release a vehicle
What this service does
Identity and permission in one check
A license record can confirm both who the holder is and what they are allowed to drive. One request can carry holder details, validity dates, covered vehicle classes and current standing. Which fields you get depends on the data source and on the license record itself.
What Basic and Advanced coverage include
Basic coverage establishes that a license exists and is current. Advanced coverage adds vehicle classes, issuing authority detail, address information and transport endorsement details where the record carries them. What either tier can return depends on your service contract.
Works for one driver or a whole roster
Fleet, delivery and mobility teams onboard drivers continuously and have to re-check them at renewal. An API check runs the same way at either scale, and the validity date in the response can drive a scheduled re-check instead of a manual audit.
Consent comes before the request
Verification is an identity check on a real person. The workflow assumes informed consent captured before the request, and use limited to the stated purpose. It also assumes retention no longer than that purpose requires, and an audit trail of who queried what.
How a check runs
Collect the license number and consent
Take the driving license number and the holder's date of birth. Capture informed consent for the check as well, with a record of the purpose you are running it for.
Clean up the license number
Strip spaces and separators and standardize the letter case before you submit. License numbers are written inconsistently across states and by applicants, and normalizing the input removes a large share of avoidable failures.
Send the license for checking
Submit the license details through the API on the coverage your service contract includes. The request is processed against the available license records.
Read the validity and the vehicle classes
Your application receives the available holder, validity, vehicle-class and status information as structured fields. Which fields come back varies by data source and by the individual license record.
Activate, hold, or send to review
Act on the result inside your own flow. Activate the driver, hold the application pending a renewal, or send a restricted or no-record outcome to manual review instead of an automatic decline.
Questions
- What is a driving license verification API?
- An interface that checks a submitted driving license number against available license records from inside your own application, instead of reviewing each card by hand. The available holder, validity and vehicle-class information comes back as structured fields.
- What do I send to check a driving license?
- The number printed on the license, usually together with the holder's date of birth. Some flows read both from a photograph of the card first. The applicant then does not have to type them at all.
- What does a driving license check return?
- Depending on the record, the response can carry the holder's name and date of birth, the issuing transport office and state, and the issue date. Validity dates, covered vehicle classes and current standing can also come back, with address and transport endorsement details on Advanced coverage. Fields returned differ by data source and by the individual license record.
- What is the difference between Basic and Advanced driving license coverage?
- Basic coverage establishes that a license resolves to an available record and reports its validity and current standing. Advanced coverage adds the covered vehicle classes, issuing authority detail, address information and transport endorsement details where the record carries them. The coverage available to you depends on your service contract.
- Does a no-record result mean the license is fake?
- No. It can follow from a mistyped or differently formatted number, a state record that is not currently available, or a recently issued license. Treat it as a prompt to re-collect the document and check again.
- Do I need the license holder's consent?
- Yes. A driving license is personal data and the check is an identity verification. Collect informed consent before the request, state the purpose plainly, use the response only for that purpose, and keep a record of the consent alongside the result.
Catalog entry last updated .