Overview
V2 consolidates trip replay into a single paginated endpoint. EachTripDto covers one continuous movement segment:
V2 uses a single
GET /v2/api/replay/{id} endpoint for all replay requests. The V1 distinction between GetReplayUserTime and GetReplay (UTC vs. user time) no longer applies — V2 always returns both timeUtc and timeUser on each point.Step 1 — Request a date range
Fetch trips for vehicle1000 over one week. Pass from and to as ISO 8601 UTC strings:
Step 2 — Inspect the response
The response is a paginated envelope. Each element initems is a TripDto:
Step 3 — Decode the encoded polyline
The encoded field uses the Google Polyline Algorithm format, supported by all major mapping SDKs.
Step 4 — Render on a map
Fetching all pages
For long date ranges, iterate through all pages:Python
Google Static Maps thumbnail
Theurl field is a pre-built Google Static Maps URL. Use it server-side to generate a trip thumbnail without decoding the polyline:
Python
Gotchas
- Distance unit:
distanceis in kilometres in V2 (V1 used metres). - Duration format:
durationis"hh:mm:ss"in V2, not ISO 8601PT...format. - Single endpoint: V2 has one replay endpoint. Both UTC and user-time fields are always returned on each point — no need to choose between
GetReplayandGetReplayUserTime. encodedformat: Google Polyline Algorithm. If your decoder produces invalid coordinates, confirm the encoding with your Telemax contact.