Prerequisites — Create an API Key
Before making any API calls, you’ll need an API key. Head to the Telemax Webhooks and API Key section in the Telemax dashboard to create your own key.Navigate to Telemax Dashboard → Webhooks and API Key to generate a new API key. Copy the key and keep it secure — you’ll use it in the step below.
Step 1 — Get an access token
V2 token endpoints are at/api/v2/authentication/token/.... Interactive reference: API key token.
Step 2 — List your companies
UseGET /api/v2/companies to discover the company IDs your token can access. The Id on the first result is your primary company ID — you’ll need it for fleet and alert endpoints.
Step 3 — Get your fleet’s last positions
UseGET /api/v2/companies/{id}/vehicles/last-position with the company ID from Step 2 to fetch the current location of every vehicle.
PositionDto list with fields including DeviceId, DeviceName, Lat, Lng, UtcTime, Speed, Ignition.
Step 4 — Fetch a single vehicle’s last position
UseGET /api/v2/vehicles/{id}/last-position for a specific vehicle by its legacy vehicle ID (DeviceId):
GET /api/v2/vehicles/{imei}/device-ids.
Common first errors
| Symptom | Cause | Fix |
|---|---|---|
401 with no body | Missing or invalid Authorization header | Obtain a fresh token; prefix with Bearer |
401 from token endpoint | Wrong password or unknown API key | Verify credentials; GUID keys must exist in ApiKeys non-deleted |
403 on a data route | Token not scoped to that company | Check GET /api/v2/companies for accessible company IDs |
404 on a vehicle route | Vehicle ID unknown or not in your company | Use POST /api/v2/vehicles/list to confirm the vehicle exists |
429 Too Many Requests | Rate limit exceeded (60 req / 60 s per token) | Wait the Retry-After header value before retrying |
Empty access_token | Parsing error | Ensure Content-Type is application/x-www-form-urlencoded, not JSON |