Get Trip Replay (User Time)
Telemetry & replay
Trip replay (user time)
Trip replay for a vehicle using the user’s time zone context.
POST
Get Trip Replay (User Time)
All routes require JWT Bearer unless noted. Vehicle
id parameters refer to the legacy vehicle id unless stated otherwise.
Overview
Returns trip replay data for a vehicle, using the same implementation asGetReplay (controller documents “user time zone”; the service normalizes from/to as UTC for queries).
A V2 version of this endpoint is available: Trip replay. New integrations should prefer V2.
Endpoint
POST /api/GetReplayUserTime
Authentication
Required. Bearer token.Request headers
| Header | Required | Description |
|---|---|---|
| Authorization | Yes | Bearer <access_token> |
Query parameters
Legacy vehicle id.
Range start (interpreted as UTC in service).
Range end (interpreted as UTC in service).
Response
200 OK —TripDto[] (List<TripDto>). Each trip includes Points (up to 400 per trip segment), Url (Google static map), Encoded polyline, Distance, Duration, StartAddress, EndAddress, StartTimeUser, EndTimeUser.
Known field issues (V1 only):
| Field | Issue |
|---|---|
Distance | Returned in km (odometer delta), not metres. A value of 11.34 means 11.34 km. |
Duration | .NET TimeSpan string ("03:05:50" or "2.04:04:21.0100000"), not ISO 8601. |
Url | Google Static Maps URL — requires a valid API key configured server-side; may return a placeholder string. |
StartTimeUser, EndTimeUser, Distance, Duration | All trips return identical values when the date range covers multiple trips. Each TripDto metadata is computed from the first/last point of the entire query window, not per-trip. Use the Points array for accurate per-trip data. Prefer V2 Trip replay which fixes this. |
Points field names use camelCase (timeUtc, timeUser, speed, direction, ignition, odo).
Error responses
| Status | Meaning |
|---|---|
| 404 | Unknown legacy vehicle id |
| 401 | Caller cannot access vehicle |
Code examples
cURL
Authorizations
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.
Query Parameters
Vehicle ID
From date and time (UTC)
To date and time (UTC)
Response
Successful response with trip replay data