Filodos

Webhooks setup

For administrators: push trip ends, zone arrivals, critical alarms, and the daily report into your own systems. Part of the documentation.

Subscribe an endpoint

  1. Prepare an HTTPS address in your system that accepts JSON POST requests, for example https://erp.example.com/filodos-hook.
  2. Sign in as an administrator and open Organization → Webhooks.
  3. Type a name, paste the address, and tick the events you want.
  4. Click Create subscription. The signing secret shows once — copy it now. Your system uses it to check that each delivery really comes from Filodos.

Every delivery carries two headers: X-Filodos-Signature (a signature of the message body made with your secret) and X-Filodos-Delivery (a unique id per delivery, so your system can ignore a repeated one). Give the full details to your developer: the webhook events reference has the message shapes and a worked check.

The five events

  • trip.ended — a trip closes, with its distance. Use it to file mileage.
  • geofence.enter and geofence.exit — a linked vehicle crosses one of your zones. Use them as delivery timestamps.
  • alarm.critical — SOS, collision, or rollover. Use it to open an incident.
  • report.daily — the nightly report e-mail run finishes, with how many e-mails went out.

Zone events only fire for vehicles linked to the zone — link them first on the Geofences page.

Retries and replay

Every push is stored before its first send. A failed send — a network error, a timeout, or a 429 or 5xx answer — retries automatically after 1 minute, 5 minutes, 30 minutes, 2 hours, and 12 hours. Any other 4xx answer fails at once: the receiver rejects the message itself, so resending changes nothing.

Open the subscription to see each delivery: sent, pending with the next retry time, or failed with the reason. Re-send any stored delivery with Replay — it goes out under a new delivery id, marked "replay": true. For developers, the same rows live at GET /webhooks/{id}/deliveries and POST /webhooks/{id}/deliveries/{delivery_id}/replay — see the webhook management reference.

Test and troubleshoot

Click Send test on the subscription row. Filodos posts a signed webhook.test ping at once and shows your system's answer. If the answer is not 200, check that the address is reachable from the internet, accepts POST, and answers within 10 seconds. Delete the subscription when you no longer need it — deletion is immediate.