NextRoute API Docs
Developer documentation for GPS device hosting, GT06/TR06-style TCP decoding, REST APIs, WebSocket streams, API key isolation, and recent location history access.
Phase 1 is focused on device data infrastructure. It is not a full fleet-management suite with dispatch, driver management, geofencing, reports, or billing automation.
Request access
Share your company, device count, GPS model, protocol, update interval, and required access.
Add GPS device
After onboarding, register the GPS device IMEI from the console Devices page.
Configure device endpoint
Point the GPS device TCP server to the NextRoute ingestion host and port provided during onboarding.
Consume location data
Use REST APIs for latest/history data or subscribe to live updates through WebSocket.
Currently supported
GT06/TR06-style TCP GPS devices.
Available on request
Other protocols can be reviewed based on device model and packet format.
Avoid assumptions
Confirm the device brand, model, protocol name, and sample packet before onboarding.
curl -H "x-api-key: <api_key>" https://api.nextroute.in/devices/live-locationswss://ws.nextroute.in/?api_key=<api_key>| Method | Endpoint | Description |
|---|---|---|
| GET | /devices | List devices registered under your company. |
| GET | /devices/:imei | Fetch one company-owned device by IMEI. |
| GET | /devices/:imei/latest | Fetch the latest known location for a device. |
| GET | /devices/:imei/history | Fetch recent stored location history for a device. |
| GET | /devices/:imei/route | Fetch recent route/location points for a device. |
| GET | /devices/live-locations | Fetch latest locations for all company devices. |
[
{
"device_id": "999999999999999",
"label": "truck-01",
"lat": 28.6152,
"lon": 77.2114,
"speed": 42,
"event_time": "2026-07-08T07:30:00.000Z"
}
]REST APIs, WebSocket access, devices, and location history are scoped by company. Customers use their own API key and can only access data belonging to their company.