Skip to main content

Overview

Trip replay returns a structured history of vehicle movement as a list of TripDto objects. Each trip covers one continuous movement segment with: Two endpoints are available:
Both endpoints treat the from and to parameters as UTC internally. The “user time” variant adjusts the display fields (startTimeUser, endTimeUser) but the query window is still UTC. Pass ISO 8601 strings (e.g. 2025-05-01T00:00:00Z).

Step 1 — Request a date range

Fetch trips for vehicle 1000 over one week:

Step 2 — Inspect the response

Each element in the returned array is a TripDto:
Long trips may be split into multiple TripDto entries capped at 400 points each. If you see the same start/end address with sequential timestamps, the trip was chunked — stitch the points arrays together and sum the distance values.

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


Google Static Maps thumbnail

The Url 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: distance is in metres, not kilometres. Divide by 1000 for km.
  • UTC always: Both GetReplay and GetReplayUserTime treat from/to as UTC. The “user time” variant only affects the display fields (startTimeUser, endTimeUser).
  • 400-point cap: Long trips are split into multiple TripDto entries. Sum distance across segments for total trip distance.
  • Encoded format: Assumed to be Google Polyline Algorithm format. If your decoder produces invalid coordinates, confirm the encoding with your Telemax contact (GAP-18).