Fleet Tracking API & Integrations
Every reading, event and report the dashboard produces is available over a REST API and webhooks. If you would rather see this data inside your own system, that is a supported path, not a favour.
VouchTrack exposes a REST API and webhooks covering live position, trip history, events, sensor readings, fleet structure and reports. Access is authenticated per account with read and command scopes kept separate. A sandbox with simulated vehicles is available before you commit, and the full reference is issued with your credentials.
Everything the dashboard knows
If a number appears on a screen in our platform, it is reachable programmatically. Where something is configured per account rather than available by default, it says so.
Live position
AvailableThe current position, speed, heading and ignition state of any vehicle or asset you are authorised to see, so your own dashboard can show what ours does.
Trip and position history
AvailableThe full track for a vehicle over a date range, including stops, idles and the gaps that were buffered on board and uploaded later.
Events and alerts
AvailableGeofence entry and exit, speeding, harsh events, tamper, power cut, door open, temperature breach — each with position, time and the rule that produced it.
Sensor readings
AvailableFuel level, temperature, humidity, water level, tyre pressure and engine hours, as a time series you can chart or reconcile against your own records.
Vehicles, drivers and groups
AvailableRead the fleet structure — registration, make, group, assigned driver — so your system and ours agree on what exists without anyone maintaining two lists.
Reports
AvailableTrigger any report the dashboard can produce and collect it as JSON, CSV or PDF, which is usually simpler than rebuilding the same calculation on your side.
Webhooks
AvailableRather than polling us, register an endpoint and we post the event to you as it happens. This is the right choice for anything that needs to act on an alert.
Commands
Enabled per accountWhere the account is configured for it, issue a speed-interlocked immobilisation or a device configuration change. Gated separately from read access for obvious reasons.
What you actually receive
Illustrative payloads, so you can judge the fit before you ask for credentials. These show the shape of the data, not the live endpoint contract — the exact schema comes with your reference.
{
"vehicle": "LES-4821",
"time": "2026-08-09T14:22:07+05:00",
"lat": 31.4697,
"lon": 74.2728,
"speed": 62, // km/h
"heading": 148,
"ignition": "on",
"driver": "A. Khan", // from the RFID card
"sensors": {
"fuel_litres": 184.2,
"temp_c": -18.4
}
}{
"event": "fuel.drop",
"vehicle": "LES-4821",
"time": "2026-08-09T02:51:33+05:00",
"rule": "drop > 20 L, engine off",
"detail": {
"litres": 78,
"duration_s": 540,
"before": 262.0,
"after": 184.0
},
"lat": 30.6682, "lon": 73.1114,
"place": "N-5, near Sahiwal"
}Two design notes worth stating plainly. Timestamps carry an explicit offset rather than assuming Pakistan Standard Time, because fleets that cross into other zones break every system that assumes otherwise. And every event names the rule that produced it, so when someone asks why they were alerted, the answer is in the payload rather than in a support ticket.
Do not poll us for something that has not happened
Most integrations start by polling positions every few seconds and end up rate-limited, expensive and still late. Register an endpoint instead and we post the event the moment the rule fires.
- Delivered as the event happens, not on your next poll
- Retried with backoff if your endpoint is down
- Signed, so you can verify the request came from us
- Filtered per subscription — take only the events you act on
Before you start
Ask before you build. We would rather spend twenty minutes on the design than have you discover a constraint in week three.
Ask a questionYes. We issue sandbox credentials with a small set of simulated vehicles producing realistic movement and events, so you can build and test without touching a live fleet or waiting for hardware.
Per-account API credentials, scoped to the vehicles and the operations that account is allowed to perform. Read access and command access are separate scopes, so an integration that only needs positions can never issue an immobilisation.
They are set per account against what your integration actually needs rather than a single published number. If you are polling frequently enough for limits to matter, webhooks are almost always the better design and we will say so.
It is issued with your credentials rather than published openly, because it describes the exact surface available to your account. Ask us and we will send the reference and a sandbox key — you do not need to be a customer first.
Yes. We run a software practice alongside the tracking business, so if your team does not have the capacity we can build and maintain the integration into your ERP, dispatch system or portal ourselves.
Your fleet data is yours. The API exists so you can take it out, and our data protection page sets out retention, access control and what happens at the end of a contract.
Ask for a sandbox key
Tell us what you are building and we will send the reference documentation and sandbox credentials. You do not have to be a customer to get them.
[email protected] · 17‑A, Bosan Road, Multan · PTA-licensed