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.
RESTful design: V2 endpoints follow standard RESTful HTTP methods (
GET, POST, PUT, DELETE) with parameters passed in the path or query string. A small number of endpoints still use POST where the parameter set is too large for a query string — see Which endpoint do I need? for per-endpoint details.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
Find the right endpoint for polling fleet positions and tracking live vehicle locations.
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.