Skip to main content
GET
Last position (V2)

Overview

Returns the most recent position record for the specified vehicle.
The V1 version of this endpoint is Vehicle Position.
Rate limit: 144,000 req/s · 144,000/min · 144,000/hr · 60/day — in practice 60 requests per day per API key

Endpoint

GET /v2/api/vehicles/{id}/last-position

Path parameters

integer
required
Public vehicle ID (deviceId).

Response

200 OK — PositionDto, or an empty HTTP 200 with no body.
The body is empty when the vehicle has no stored position, or has not yet completed an ignition-on or ignition-off period (for example a tracker with no ignition input). Fleet last positions, List vehicles and Nearest vehicles may still show such a vehicle. Check for an empty response before parsing; it is not JSON null.
This table is the reference for PositionDto on every endpoint that returns it. List vehicles, Fleet last positions and Nearest vehicles build it from the server’s cached vehicle state rather than from the latest stored record, so a few fields mean something different there. Those rows say so under “list, fleet, nearest”; “this endpoint” means Last position. Record & timestamps Location Engine & power Signal Device & identity Movement history Trip & driver
Which points the movement fields read. A route record is one ignition-on or ignition-off period. This endpoint reads the current and the previous route record; list, fleet and nearest read only the last completed one. The values depend on whether the device keeps reporting while parked, so treat them as indicative, not as trip boundaries. For completed trips use Trip replay; the trip in progress is only reflected on this endpoint.
Fuel Electric vehicle null when the vehicle does not report them. Hybrids can report them too. Connected-car (Compass) vehicles never fill batteryLevel; their battery charge is in fuelLevel. Vehicle state Connectivity Request metadata

Error responses

Authorizations

Authorization
string
header
required

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

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

Scoping: API key tokens are scoped by the key's company and its action set; see Token scoping.

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

Path Parameters

id
integer
required

Response

Successful response