Toll Tag Status API
New
Get the FASTag details recorded against a vehicle registration number, and use the result inside your fleet, leasing, lending or insurance workflow.
Overview
A FASTag is the tag carried on a vehicle's windscreen for electronic toll payment on Indian highways. It is issued against one registration number and one declared vehicle class. That makes the tag record a useful reference for anyone who needs to know whether a vehicle is set up to move. Fleet, leasing, lending and insurance teams often need that answer before an asset is dispatched, financed or handed over. Asking the owner for a screenshot is slow, and a screenshot only states what the owner says is true. Your application sends a vehicle registration number and gets the available tag information back as structured data. Which fields come back depends on the data source, the vehicle record and the service contract you select.
- Category
- Vehicle Services
- Coverage
- Vehicles registered in India that carry an issued toll tag
- Input
- Vehicle registration number
- Output
- Toll tag details available for that vehicle, as structured data
- Typical users
- Fleet operators, lenders, insurers, leasing companies, fintech platforms
- Coverage note
- Limited to what the underlying toll tag data source holds for that vehicle
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 | Optional | — | Matches ^[A-Z0-9]+$. 5 to 12 characters |
input. | string | Optional | — | Matches ^[A-Z0-9]{1,25}$ |
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/fastag-details \
-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/fastag-details", {
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/fastag-details",
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 or any or null | Always | The registration number sent; null when the lookup was by tag id. | — |
data. | string or any or null | Always | The tag id sent; null when the lookup was by registration number. | — |
data. | object or any or null | Always | The tag in force: an active tag before an inactive one, then the latest issued. null when there is no tag. | — |
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: checking tag state before a vehicle is dispatched on a tolled route
- Vehicle finance: reviewing whether a financed commercial vehicle is tagged and in service
- Insurance: comparing the class declared on the tag with the vehicle presented for cover
- Rental and leasing: checking the tag before handover and again on return
- Fintech and fleet cards: reviewing a tag position before enrolling a vehicle
- Used-vehicle marketplaces: surfacing tag state during inspection and listing review
What this service does
FASTag details you can get back
Whether a tag is recorded against the registration number, the status carried on it, the vehicle class it was issued against, and issuance-related details. Where the service contract you select supports it, toll usage information may also be available. The exact fields differ by data source, by vehicle record and by that contract.
Nothing to upload
You start from a registration number your team already has on file. There is no document to send and nothing to request from the driver first.
A check at dispatch, disbursal or handover
Connect the API to a fleet system, a lending application, a leasing platform or an inspection tool. The tag is then reviewed at the moment a vehicle moves, instead of in a separate queue afterwards.
The same check across a fleet
Checking tags by hand gets harder as vehicle counts rise. An API workflow applies the same check to every registration number, whether your team reviews a handful a week or sweeps a whole fleet on a cycle.
How a check runs
Arrange access for tag checks
Tell us where the tag check belongs in your process. We arrange access for your organization under the applicable service contract.
Send the vehicle number
Your application sends the registration number of the vehicle you need toll tag information for.
The tag record is retrieved
The service processes the submitted registration number and pulls the toll tag information available for that vehicle.
Read the tag details
Your application receives the available tag details in a structured response.
Clear the vehicle to move
Route the outcome into the dispatch, financing, underwriting or handover step it was requested for, and store it with the decision it supported.
Questions
- What do I send to check FASTag status?
- The vehicle registration number. There is no document upload and nothing to collect from the driver before you make the request.
- What does a toll tag status response include?
- You get the tag information available for that registration number: whether a tag is recorded, the status on it, the class it was issued against and issuance-related details. Toll usage information may also be available where your service contract supports it. Which fields appear differs by data source, by vehicle record and by that contract.
- Does an inactive FASTag mean something is wrong with the vehicle?
- Not on its own: treat the status as a prompt to review the record. The class on the tag may not match the vehicle, or the vehicle or customer details at the issuing institution may be incomplete or expired. The tag may also be carried loose rather than stuck to the windscreen, or reported lost or damaged.
- Do I need consent to check a FASTag on someone's vehicle?
- A tag record can be linked through the registration number to an identifiable person. Run the check on a lawful basis, adding the consent of the person concerned where your process calls for it. Use what comes back for that purpose alone, and keep it visible to the team whose work needs it.
- Can I check FASTag status across a whole fleet at once?
- A scheduled sweep across the registration numbers you already hold is a common pattern for fleet, leasing and rental operators. It gives your team a dated record of what each tag showed. What your volumes can support depends on the service contract you select.
- How do I get access to the toll tag status API?
- Start with Get API and tell us how tag checks fit your fleet or lending process, and what volumes you expect. We confirm what the service can support and set up access under the applicable service contract.
Catalog entry last updated .