Technology · TEC-01E · REST · Consent-based · Business use
A phone tracking API does one job well: given a mobile number and the number holder's consent, it returns that phone's live location to your application. For logistics apps, field-force tools and delivery platforms, that is often the only location primitive you need — no SDK on the end-user's phone, no device to ship, no per-user hardware.
What it is — and isn't
This is a business capability for locating drivers, delivery agents and field employees who have consented to be tracked for a trip or shift. It is delivered as a clean API you call from your own backend, and the platform runs the consent workflow so your application never handles that sensitive step alone.
It is explicitly not a covert tracing tool. No location is returned for a number whose holder has not granted logged consent, and sessions are scoped to the business engagement. Those constraints are a feature, not a limitation — they are what keep your product on the right side of the line.
For product teams
Submit a number, receive coordinates, accuracy, operator and status as predictable JSON.
Resolve many numbers in a single call for fleet- and platform-scale polling.
The platform triggers, captures and logs consent; you poll a status endpoint and track only ready numbers.
Receive geofence and deviation events as push callbacks instead of polling for them.
Build against test numbers with a technical account manager before you go live.
Airtel, Jio and Vi behind one contract — no carrier branching in your code.
Use cases
The phone tracking API adds a verified, consent-based location to workflows where you need to know where a person or vehicle is — without asking them to install your app.
Show live ETAs for drivers who will not install another app.
Confirm a technician reached the customer’s address before closing a job.
Verify a surveyor or claimant’s location at the time of inspection.
Record that a field agent visited the borrower’s location.
Mark on-site attendance for staff who work away from an office.
Track hired buses and cabs whose drivers you don’t employ directly.
Clear boundaries
Phone location is sensitive, so the limits are built into the platform rather than left to policy.
Lost your own phone? Report it to the police and block it through the government’s Sanchar Saathi portal — that is the right route for personal devices.
Questions
They share the same platform and endpoints. 'Phone tracking API' simply describes the same consent-based capability from the perspective of locating a phone number inside your own app.
No. The API returns no location for any number whose holder has not granted logged consent. This is enforced by the platform.
No SDK is required on the tracked phone. Location is resolved over the network once consent is granted.
Yes, the bulk endpoint handles many numbers per call, which is the right pattern for fleet and platform use.
No. Location is resolved by the mobile network, not by an app running on the phone, so there is no extra battery use on the device.
Yes, and on basic feature phones too. Because nothing runs on the handset, the phone’s operating system does not matter.
Yes. Consent can be withdrawn at any time, and tracking for that number stops when it is.
For a business tracking its own drivers, staff or contracted vehicles with their informed consent, yes. Consent is logged for every number, in line with Indian telecom norms and the Digital Personal Data Protection Act, 2023.
Book a demo
Share what you're building and your expected volume, and our integration team will provide documentation, sandbox access and support to take you to production.