Technology · TEC-01A · REST · JSON · Bulk lookups · Consent built in
If you already run a transport management system, a delivery app or an internal operations console, you don't need another dashboard — you need location as data. The SIM Tracking API exposes consent-based cellular location as a straightforward REST endpoint your engineers can call in an afternoon, so live positions appear inside the software your teams already use.
What it does
Submit a mobile number; receive a latitude, longitude, accuracy radius and resolving operator in a structured JSON response. The API abstracts away every operator-specific quirk behind one consistent contract, so your code never has to know whether a number sits on Airtel, Jio or Vi.
Consent is handled by the platform, not by you. When a number is first submitted, the consent workflow fires automatically; your application simply polls for a ready state and then queries position at whatever cadence your use case demands.
For engineers
Every response carries coordinates, accuracy, operator and a status field. No parsing surprises, no undocumented edge cases.
Submit up to 500 numbers in one request and receive all positions in a single response — built for fleet-scale polling without rate-limit gymnastics.
Query the consent status of any number programmatically and re-trigger the workflow for non-responders, all through the API.
Subscribe to geofence entry, exit and route-deviation events and receive them as push callbacks rather than polling for them.
Develop against a sandbox with test numbers before you touch production traffic or billing.
Every call, its resolving operator and its outcome are logged for your finance and operations teams to audit.
Integration path
Endpoints at a glance
Every call is a standard HTTPS request with a JSON response, authenticated with a short-lived bearer token. These are the building blocks most integrations use.
| Capability | What it does | Typical use |
|---|---|---|
| Authentication | Issues a bearer token for your API credentials | Called by your backend before other requests |
| Single location lookup | Returns the current position of one consented number | On-demand “where is this truck now?” |
| Bulk location lookup | Up to 500 numbers in one request | Fleet-wide polling on a schedule |
| Consent request and status | Starts the SMS, IVR, missed-call or web-link consent flow and reports its state | Onboarding a new driver or a market vehicle |
| E-Way Bill, FASTag, RC and DL checks | Compliance data from India’s transport systems, on the same credentials | Pre-dispatch checks and in-transit alerts |
Build or buy
Location from the mobile network is not a public API. Building it in-house means separate agreements and integrations with each operator, plus a consent system that will stand up to audit.
Building a full product around it? See the SIM-based tracking system, which adds a ready-made dashboard on top of the same API.
API questions
A standard REST API returning JSON. Each response includes latitude, longitude, an accuracy radius, the resolving operator and a status field.
Yes. The bulk endpoint accepts up to 500 mobile numbers per call and returns all coordinates in one response, which is the right pattern for fleet-scale polling.
The platform manages consent. You submit numbers, the consent workflow runs automatically, and you poll a status endpoint before tracking. You can also re-trigger consent for non-responders programmatically.
Yes — you build and test against a sandbox with test numbers before moving to production credentials and live billing.
A single location lookup typically returns in under a second. Bulk requests return all positions for up to 500 numbers in one response.
By the number of mobile numbers you track per month, with volume pricing above 1,000 numbers. There is no setup fee.
Most teams move from sandbox credentials to production in 3–7 days. Our integration team supports you through testing and go-live.
Yes. Vehicle registration (VAHAN), driving licence (SARATHI), E-Way Bill and FASTag data are available on the same credentials as location.
Book a demo
Tell us your stack and expected query volume, and we'll share endpoint documentation, sandbox credentials and a technical account manager to get you to production quickly.