Skip to main content
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 as GetReplay (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

Query parameters

integer
required
Legacy vehicle id.
string (datetime)
required
Range start (interpreted as UTC in service).
string (datetime)
required
Range end (interpreted as UTC in service).

Response

200 OKTripDto[] (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): Points field names use camelCase (timeUtc, timeUser, speed, direction, ignition, odo).

Error responses

Code examples

cURL

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

Content-Type
string
Authorization
string
required

Bearer your_token

Query Parameters

id
integer
required

Vehicle ID

from
string
required

From date and time (UTC)

to
string
required

To date and time (UTC)

Response

Successful response with trip replay data