Skip to main content
GET
/
api
/
GetDeviceId
/
{imei}
Resolve IMEI
curl --request GET \
  --url https://api.telemax.com.au/api/GetDeviceId/{imei} \
  --header 'Authorization: Bearer <token>'
{
  "vehicleId": 123,
  "vehicleName": "<string>"
}

​
Overview

Resolves a device IMEI to legacy vehicle id and name for vehicles the caller may access.
A V2 version of this endpoint is available: Device ID from IMEI. New integrations should prefer V2.

​
Endpoint

GET /api/GetDeviceId/{imei}

​
Path parameters

​
imei
string
required
Tracker IMEI (digits as stored in Telemax).

​
Response

200 OK — ImeiSearchResultDto
FieldTypeDescription
vehicleIdintegerLegacy vehicle id
vehicleNamestringVehicle display name

​
Error responses

StatusMeaning
404IMEI not found
401Vehicle not allowed for caller

​
Example response

{
  "vehicleId": 88421,
  "vehicleName": "Delivery Van 07"
}
cURL
curl "https://api.telemax.com.au/api/GetDeviceId/353148090123456" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."

Authorizations

​
Authorization
string
header
required

JWT Bearer token obtained from POST /api/authentication/token/user or POST /api/authentication/token/api-key.

Lifetime: ~24 hours (86,399 seconds). Cache the token and reuse it. Re-authenticate 5 minutes before expiry.

Scoping:

  • User tokens are scoped to a single company.
  • API key tokens may restrict access to a vehicle allowlist and/or action set (see token claims).

No refresh endpoint — re-authenticate with your credentials when the token expires.

Headers

​
Authorization
string
required

Bearer your_token

Path Parameters

​
imei
string
required

Tracker IMEI

Response

Successful response

​
vehicleId
integer
​
vehicleName
string