Filodos

Events

Stored driving events per vehicle or per driver, most recent first. Needs the events:read scope on API keys. Part of the documentation.

GET/events

Lists one vehicle's stored events: severity 2 and 3, plus zone entries and exits regardless of their own severity 1 (so zone filters keep working). For instant pushes instead of polling, see webhook events.

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

[{"id": 905, "trip_id": 812, "device_id": 43, "event_type": "overspeed",
  "occurred_at": "2026-10-05T06:20:00+00:00", "severity": 2,
  "attributes": {}}]
ParameterRequiredNotes
device_idYesTraccar device id from GET /devices. Another org's id reads 404.

attributes carries type-specific detail: geofenceId on zone events, the alarm name on alarms, a map-marker position id on camera-detected alerts.

GET/driver/events

Lists one driver's stored events across every vehicle they drove — newest first, same shape as GET /events. Attribution follows the driver↔vehicle assignment history: an event counts for whoever was linked when it occurred.

curl 'https://filodos.gr/filodos-dashboard/api/scoring/driver/events?traccar_driver_id=12&limit=50' \
  -H "Authorization: Bearer filodos_…"
ParameterRequiredNotes
traccar_driver_idYesDriver id from your driver records. Unknown ids read 404.
limitNo1–1000 rows per call; default 200.

Event types

Severity runs from 1 (minor) to 3 (critical). The names below are Traccar's stable event-type constants, not protocol message ids.

TypeSeverityNotes
sos, collision, rollover3Critical alarms. Each also fires an alarm.critical webhook.
fatigueDriving, overspeed, deviceOverspeed2Serious driving events.
adasAlarm, hardAcceleration, hardBraking, hardCornering2Camera and harsh-manoeuvre detections.
geofenceEnter, geofenceExit1Zone crossings of linked vehicles. Each fires a webhook too.