API Reseller
FASTag API
FASTag recharge and balance enquiry keyed on the vehicle registration number, plus new tag issuance where the issuer supports it.
What you get
- Recharge by vehicle registration number
- Balance enquiry across issuers
- New tag issuance where supported
- Toll transaction history retrieval
- Low-balance webhooks per vehicle
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Key
- Vehicle registration number. No tag ID needed from the customer.
- Operations
- Recharge, balance enquiry, toll history, issuance where supported.
- Webhook
- Low-balance notifications per registered vehicle, signed as above.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About fastag api
The customer knows their vehicle number but not their tag ID. Is that enough?
Yes. Every operation is keyed on the vehicle registration number, and the tag is resolved from it. Asking a customer for a tag ID at a counter is a step that mostly produces wrong answers.
What if the vehicle has no FASTag yet?
Issuance is available where the issuer supports it, and the lookup tells you whether it is. A vehicle with no tag returns a clear not-found rather than an error, so your product can offer issuance at that point.