GPS device data infrastructure

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.

Quick Start
Phase 1
1

Request access

Share your company, device count, GPS model, protocol, update interval, and required access.

2

Add GPS device

After onboarding, register the GPS device IMEI from the console Devices page.

3

Configure device endpoint

Point the GPS device TCP server to the NextRoute ingestion host and port provided during onboarding.

4

Consume location data

Use REST APIs for latest/history data or subscribe to live updates through WebSocket.

Phase 1 Capabilities
GPS device hosting
GT06/TR06 decoding
Live WebSocket feed
API key isolation
15–30 day retention
Basic operator console
Supported Devices & Protocols
GT06/TR06-style TCP

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.

Authentication
x-api-key
REST API Example
curl -H "x-api-key: <api_key>" https://api.nextroute.in/devices/live-locations
WebSocket URL
wss://ws.nextroute.in/?api_key=<api_key>
REST Endpoints
Base URL: https://api.nextroute.in
MethodEndpointDescription
GET/devicesList devices registered under your company.
GET/devices/:imeiFetch one company-owned device by IMEI.
GET/devices/:imei/latestFetch the latest known location for a device.
GET/devices/:imei/historyFetch recent stored location history for a device.
GET/devices/:imei/routeFetch recent route/location points for a device.
GET/devices/live-locationsFetch latest locations for all company devices.
Example Response
/devices/live-locations
JSON
[
  {
    "device_id": "999999999999999",
    "label": "truck-01",
    "lat": 28.6152,
    "lon": 77.2114,
    "speed": 42,
    "event_time": "2026-07-08T07:30:00.000Z"
  }
]
Tenant Isolation

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.