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.
Key capabilities
- Authentication: API key returning a Bearer JWT with company, timezone, and action claims.
- Telemetry: last position, historical positions, trip replay (each point carries UTC and API-key-time-zone timestamps), IMEI lookup, nearest-vehicle search, and fleet-wide snapshots.
- Commands: odometer update (including the odometer source) and vehicle rename.
- Alerts: list alerts with reverse geocoding; mark one as read or unread, or mark all alert records (the 10 types in Alert records) across your token’s companies as read.
- Insights: paged battery health scores.
- Diagnostics: engine codes from the vehicle’s latest engine-fault record.
RESTful design: V2 endpoints follow standard RESTful HTTP methods (
GET, POST, PUT, DELETE) with parameters passed in the path or query string. The token endpoint takes a form body, and POST /v2/api/vehicles/list and the webhook POST/PUT routes take a JSON body — see Content types.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.