Who it’s for
- Integration partners building billing, dispatch, or analytics on top of Telemax fleet data.
- Mobile and backend clients that authenticate with company API keys.
- Operators and developers maintaining automation against the same contracts as the legacy Telemax integration surface.
Key capabilities
- Authentication: API key returning a Bearer JWT with company, timezone, and optional vehicle and action claims.
- Telemetry: last position, historical positions, trip replay (UTC or user-time-oriented callers), IMEI lookup, nearest-vehicle search, and fleet-wide snapshots.
- Commands: odometer update, vehicle rename, and location update handoff (where IMEI exists).
- Alerts: list alerts with reverse geocoding, mark one or all as read for permitted companies.
- Insights: paged battery health predictions.
- Diagnostics: latest engine codes from vehicle handler state.
POST-first design: Almost all Telemax API endpoints use
POST regardless of whether the operation reads or writes data. Parameters are passed as query string values, not a JSON request body. The two exceptions that use GET are GetDeviceId (IMEI lookup) and devices/{deviceId}/dtc-codes (DTC code retrieval). If your HTTP client defaults to GET for read operations, you will need to override the method explicitly.Quickstart
Obtain a JWT and call your first authenticated route.
API Reference
Endpoint guides with interactive Try it for each route—start with authentication.
Guides
Real-Time Fleet Tracking
Poll fleet positions and render live vehicle locations on a map.
Trip Replay
Fetch trip waypoints, decode polylines, and render on Google Maps or Leaflet.
Alert Monitoring
Poll, filter, and acknowledge alerts in a stateful pipeline.
Vehicle Health Dashboard
Combine position, battery health, and engine codes into a single dashboard view.