NOT_FOUND / PATH_NOT_FOUND

HTTP status: 404 · Code: NOT_FOUND, PATH_NOT_FOUND

Example

{
  "type": "RESOURCE",
  "code": "NOT_FOUND",
  "description": "Vehicle was not found.",
  "requestId": "0HNP2MAV4BUCG:00000002",
  "docUrl": "https://docs.telemax.com.au/errors/not-found"
}

Cause

NOT_FOUND: the resource in the request does not exist, or is not in the companies your token can access. PATH_NOT_FOUND: the URL path matches no V2 endpoint (description “The requested path does not exist.”). This response has no rate-limit headers.

What to do

Check the ID. Company IDs come from GET /v2/api/companies. A vehicle’s ID can be looked up by IMEI with GET /v2/api/vehicles/{imei}/device-ids.
For PATH_NOT_FOUND, check the path against Which endpoint do I need?.

See Error handling for the full error model.

​Example

​Cause

​What to do

Example

Cause

What to do