Trips

One continuous drive per record, most recent first. Needs the trips:read scope on API keys. Part of the documentation.

GET /trips
GET /driver/trips

GET/trips

Lists one vehicle's segmented trips. A trip starts at ignition-on and ends at ignition-off, a 10-minute data gap, or the newest fix when still driving (ended_at: null). Poll per vehicle on your schedule, or take trip.ended pushes instead of polling.

curl 'https://filodos.gr/filodos-dashboard/api/scoring/trips?device_id=43' \
  -H "Authorization: Bearer filodos_…"

[{"id": 812, "device_id": 43, "started_at": "2026-10-05T06:02:11+00:00",
  "ended_at": "2026-10-05T06:47:03+00:00", "distance_km": 24.6,
  "start_point": {"latitude": 37.98, "longitude": 23.73, "address": null},
  "end_point": {"latitude": 38.02, "longitude": 23.81, "address": null}}]

Parameter	Required	Notes
`device_id`	Yes	Traccar device id from `GET /devices`. Another org's id reads `404`.

GET/driver/trips

Lists the trips one driver started, across every vehicle they drove — newest first. Attribution follows the driver↔vehicle assignment history: a trip counts for whoever was linked when it started. Same shape as GET /trips.

curl 'https://filodos.gr/filodos-dashboard/api/scoring/driver/trips?traccar_driver_id=12&limit=50' \
  -H "Authorization: Bearer filodos_…"

Parameter	Required	Notes
`traccar_driver_id`	Yes	Driver id from your driver records. Unknown ids read `404`.
`limit`	No	1–1000 rows per call; default 100.