Predictable REST
Resource URLs, JSON, standard verbs and status codes. One OpenAPI 3.1 document describes all of it, generated from the code that serves it.
Build on Fleet
Get fleet costs into your ERP, and connect fuel cards, telematics and workshop systems, with a modern REST API, signed webhooks and scoped keys.
Safe to retry
Every write accepts an Idempotency-Key. Retry a timed-out request and it runs at most once.
Scoped keys
Give each integration its own key with only the access it needs, an optional IP allowlist and expiry. Roll keys without downtime.
Sync-friendly
Cursor pagination and updated_since on every list make incremental sync a single loop.
What you can build
Section titled “What you can build”Fleet costs in your ERPFuel, maintenance, tyres, renewals and expenses into Odoo or Business Central: once, coded, reconciled.
Approve in Fleet, buy in OdooFleet requests go to Odoo for PR, PO and bill; the outcome comes back.
Import fuel-card transactionsBatch-create fuel logs from your card provider, without duplicates.
Stream GPS positionsSend positions and odometer readings from any telematics platform.
Sync vehicles with your ERPKeep your asset register and Fleet in step, both ways.
Run workshop jobsOpen work orders, add parts and labour, close them out.
Built for AI assistants too
Section titled “Built for AI assistants too”Every page has Copy page and Open in Claude / ChatGPT buttons, and the whole site is available as
/llms.txt and /llms-full.txt. Point your coding assistant at
/openapi.json and it knows every endpoint.