Challan Checking or Monitoring API
Fleet ready
Look up the traffic-violation records available for a vehicle, and feed the result into your fleet, lending or rental workflow.
Overview
Challan checking reviews the traffic-violation records recorded against a vehicle. You may need those records when you value a vehicle, run a fleet, process financing, handle rentals or support insurance work. An API puts challan verification inside your own application. Your application calls the API and reads the available information in a structured format. If you manage many vehicles, ongoing monitoring can be more practical than checking each vehicle by hand again and again. Monitoring works where the underlying API supports monitoring or notification features.
- Category
- Vehicle Services
- Coverage
- India
- Input
- Vehicle registration number
- Output
- Structured challan records, where available
- Typical use
- Fleet, rental, financing, resale
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 to 12 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/vehicle/challans \
-H "X-Api-Key: $FINSOUR_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"input": {
"registrationNumber": "<registrationNumber>"
}
}'Node.js
const response = await fetch("https://gateway.staging.finsour.io/v1/vehicle/challans", {
method: "POST",
headers: {
"X-Api-Key": process.env.FINSOUR_API_KEY,
"Idempotency-Key": crypto.randomUUID(),
"Content-Type": "application/json",
},
body: JSON.stringify({
"input": {
"registrationNumber": "<registrationNumber>"
}
}),
});
console.log(response.status, await response.json());Python
import os
import uuid
import requests
response = requests.post(
"https://gateway.staging.finsour.io/v1/vehicle/challans",
headers={
"X-Api-Key": os.environ["FINSOUR_API_KEY"],
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"input": {
"registrationNumber": "<registrationNumber>",
},
},
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 to 12 characters |
data. | array of objects | Always | Every challan on record, open ones first and each group in the order the source lists them. | — |
data. | string or null | Always | The challan's number, as the traffic authority issued it. | — |
data. | string or null | Always | When the challan was issued: RFC 3339 UTC. The authority records Indian Standard Time; Finsour converts. | Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}Z$ |
data. | string | Always | — | One of PENDING, DISPOSED |
data. | string or null | Always | The fine, in paise, as a decimal string ("150000" is Rs 1,500). | Matches ^(?:0|[1-9][0-9]{0,18})$ |
data. | array of strings | Always | What the challan was issued for, one sentence per offence; [] when the record states none. | — |
data. | string or null | Always | Where the offence was recorded, as the authority gives it. | — |
data. | string or null | Always | The two-letter code of the state that issued the challan. | — |
data. | string or null | Always | The issuing department (for example Traffic), as given. | — |
data. | boolean or null | Always | Whether the challan has been sent to a court, real or virtual; null when the record does not say. | — |
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
- Fleet management companies
- Vehicle rental companies
- Banks and NBFCs
- Insurance companies
- Used-car marketplaces
- Vehicle dealerships
- Fintech and automotive platforms
What this service does
Fields a challan response can include
A response can include the challan number, vehicle registration number, challan status, challan amount, offence information, date of offence, payment status and other available violation details. What comes back can vary with the records available and with the data sources the service supports.
Challan checks that run inside your own software
Connect the API to websites, mobile applications, dashboards, CRM systems, fleet platforms, lending applications and automotive software. Each check then runs in place instead of on its own.
Monitoring across a vehicle portfolio
A monitoring workflow can flag newly available challan information for a portfolio of vehicles. That is more practical than checking each vehicle by hand again and again.
More vehicles without more checkers
Manual verification gets slow once you process multiple vehicles. An API workflow scales with the number of vehicles rather than the number of people checking them.
One input into a wider vehicle decision
Available challan information can feed vehicle evaluation, risk assessment, fleet work and transaction workflows. It sits alongside the other checks those decisions rely on.
How a check runs
Send the vehicle registration details
Your application provides the required vehicle registration information in the API request.
The API checks the challan records
The API processes the vehicle information you sent and checks the challan records available for that vehicle.
Get the challan records back
Your application receives the available challan information in a structured API response.
Act on the records in your workflow
You can feed the returned data into fleet management, lending, rental, insurance, automotive or other authorised business workflows.
Questions
- What is a Challan Checking or Monitoring API?
- It is an interface for vehicle challan verification that plugs into your own applications and workflows.
- What does challan verification check?
- It checks the traffic-violation records available for a vehicle. You can review details such as challan status, amount, offence and payment status, where those are available.
- How does the challan checking API work?
- Your application sends the required vehicle information. The system processes the request and returns the available challan information in a structured response.
- Can I check challans with only the vehicle registration number?
- Yes. Where the API supports it, you can start a challan check with the vehicle registration number.
- What is an e-challan checking API?
- It handles electronic challan verification and connects it to your applications and digital workflows.
- Can I check e-challan status online through an API?
- Yes. An API workflow retrieves the available e-challan information and returns the status for review inside your application.
- How do I check a vehicle challan without a manual search?
- Send the required vehicle information to the verification service and review the records it returns. You avoid a manual search for each vehicle.
- Who can use a challan verification API?
- Fleet operators, rental companies, lenders, NBFCs, insurance providers, dealerships, automotive marketplaces, fintech platforms and other businesses can use it for appropriate business purposes.
- Can I add challan checking to an application I already run?
- Yes. You can integrate the service with websites, mobile applications, dashboards, fleet-management systems, lending platforms and other software, subject to the technical documentation provided at onboarding.
Catalog entry last updated .