domain: developer.fleetio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a webhook with POST /webhooks, specifying the destination URL and the event(s) to subscribe to from Fleetio's webhook event catalog.
List configured webhooks with GET /webhooks, retrieve one with GET /webhooks/:id, and update its URL or subscribed events with PUT or PATCH /webhooks/:id.
Have your receiving endpoint respond with an HTTP 200 within 30 seconds of each delivery, since any other response code or a timeout is treated as a failed delivery.
Verify incoming messages are authentic by computing the HMAC SHA-256 digest of the raw request body using the webhook's shared secret key and comparing it to the X-Fleetio-Webhook-Signature header.
Delete a webhook with DELETE /webhooks/:id when it's no longer needed.
Known gotchas
Webhook events are asynchronous and debounced — rapid repeated updates to the same record within a short window may be collapsed into a single delivered event, while creation and deletion events are sent as soon as possible.
After 3 consecutive failed deliveries, Fleetio automatically disables the webhook and emails the account owner and webhook creator; you must manually re-enable it after fixing your endpoint.
Failed deliveries are retried on a backoff schedule over roughly the first hour and then hourly for up to 24 hours before being marked permanently failed, and webhook event history is retained for only 30 days.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?