FASTag Transactions API
New
Read the toll crossings recorded against a vehicle's FASTag in the last 72 hours, then reconcile trips, toll spend and delivery records in your fleet workflow.
Overview
Every time a tagged vehicle passes a toll lane, the toll system records the crossing against its FASTag: the plaza, the time it was read, the lane direction and the vehicle type charged. Fleet, logistics and leasing teams often need those crossings to settle a question about a trip. Did the vehicle take the route it was dispatched on? Does the toll spend on the statement match the trips that ran? A driver's account of the journey is slow to collect and hard to check. Your application sends a vehicle registration number or a chassis number and gets back the crossings recorded in the last 72 hours 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 with an issued FASTag; crossings from the last 72 hours
- Input
- Vehicle registration number or chassis number
- Output
- Toll crossings from the last 72 hours: time read, plaza, coordinates, lane direction and vehicle type
- Typical users
- Fleet operators, logistics companies, leasing and rental businesses, transport finance teams
- Coverage note
- Limited to the crossings the toll system holds for that vehicle in the last 72 hours
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]+$. 5 to 20 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/fastag-transactions \
-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-transactions", {
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-transactions",
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 chassis number. | — |
data. | string or any or null | Always | The chassis number sent; null when the lookup was by registration number. | — |
data. | array of objects | Always | The crossings in the last 72 hours, in the order the toll system reports them; empty when there are none. | — |
data. | string or any or null | Always | When the plaza's reader read the tag. | — |
data. | string or null | Always | The plaza's name as the toll system records it. | — |
data. | string or null | Always | The lane's direction, as the toll system states it (for example N). | — |
data. | string or null | Always | The toll system's vehicle class code for the crossing (for example VC7), as given. | — |
data. | string or null | Always | The toll system's identifier for the crossing. | — |
data. | number or null | Always | The plaza's latitude in decimal degrees; null when the toll system gives no plain latitude. | Minimum -90. Maximum 90 |
data. | number or null | Always | The plaza's longitude in decimal degrees; null when the toll system gives no plain longitude. | Minimum -180. Maximum 180 |
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 operations: confirming a trip followed its dispatched route before close-out
- Toll reconciliation: matching statement charges to crossings and trips
- Logistics disputes: showing when a vehicle passed a toll plaza
- Leasing and rental: reviewing recent movement of an owned asset where the agreement allows
- Transport finance: checking toll spend against the trips that ran
What this service does
Crossings from the last 72 hours
Each crossing recorded against the vehicle's tag in the window: when it was read, the plaza's name and coordinates, the lane direction, the vehicle type charged and the sequence number. Fields differ by data source, vehicle record and service contract.
Look up by registration or chassis number
Send the registration number, or the chassis number where that is the identifier your records hold. There is no document to upload.
An empty list is an answer
When no crossing was recorded in the window, the response says so with an empty list, which your workflow can route like any other result.
The same check for every vehicle
Run it at trip close-out, on a statement cycle or when a dispute comes in, and every vehicle in the fleet is checked the same way.
How a check runs
Arrange access
Tell us where toll crossings fit in your fleet or logistics process. We arrange access for your organization under the applicable service contract.
Send the vehicle identifier
Your application sends the registration number or the chassis number of a vehicle you own, operate or have a lawful basis to check.
The crossings are retrieved
The service reads the toll crossings recorded against the vehicle's tag in the last 72 hours.
Read the crossings
Your application receives the crossings as a structured list, in the order the toll system reports them.
Close the trip or the dispute
Route the result into the trip close-out, reconciliation or dispute it was requested for, and store it with that record.
Questions
- What do I send to read FASTag transactions?
- The vehicle's registration number, or its chassis number. There is no document upload and nothing to collect from the driver first.
- How far back do the crossings go?
- The check returns the crossings recorded in the last 72 hours. Place the call close to the trip or statement you need to explain, and keep the result if you will need it later.
- What does each crossing include?
- When the tag was read, the toll plaza's name and coordinates, the lane direction, the vehicle type the plaza recorded and the crossing's sequence number. Which fields appear depends on the data source, the vehicle record and your service contract.
- What if no crossings come back?
- An empty list means no crossing was recorded against that tag in the last 72 hours. Check the identifier you sent before you treat it as a finding.
- Can I check any vehicle?
- Toll crossings show where a vehicle has been, which can point to a person. Check vehicles you own or operate, or where the person concerned has agreed for a stated purpose, and use the result only for that purpose.
- How do I get access to the FASTag Transactions API?
- Start with Get API and tell us how toll crossings fit your fleet or logistics 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 .