Coming from Fleetio
If you have built on Fleetio’s API, most of what you know carries over. This page maps the concepts and resources, and points out where Fleet behaves differently.
Conventions
Section titled “Conventions”| Fleetio | Fleet | |
|---|---|---|
| Base URL | https://secure.fleetio.com/api |
https://api.get-fleet.com/v1 |
| Credentials | Authorization: Token <key> and Account-Token: <account> |
Authorization: Bearer flt_live_…. The key belongs to one organization, so there’s no second header. Test keys start with flt_test_. |
| Versions | X-Api-Version: 2025-05-05 |
Fleet-Version: 2026-11-01; without it, the version pinned to your key |
| Pages | per_page, start_cursor → { records, next_cursor } |
limit, cursor → { data, has_more, next_cursor } |
| Filters | filter[field][op]=…, sort[field]=asc |
Named parameters (vehicle_id=, date_from=, status=), updated_since=, q=, sort=-date |
| Your ids | external_ids on vehicles; /vehicles/accounting_id:987 |
external_ids on vehicles, branches, vendors, users, contacts, parts, purchase orders and every cost record; /vehicles/odoo:77; external_id=odoo:77 filters; dedupe on create |
| Retries | — | Idempotency-Key on every write |
| Errors | JSON message | RFC 9457 problem details with a stable code |
| Webhooks | HMAC-signed, events like fuel_entry_created |
Standard Webhooks signing, events like fuel_log.created (all types) |
| Files | Upload policy, then attach a file_url |
One multipart request to …/{id}/attachments (Files) |
| First call | GET /users/me |
GET /v1/me |
Resources
Section titled “Resources”| Fleetio | Fleet | Notes |
|---|---|---|
| Vehicles | /v1/vehicles |
Groups are branches (/v1/branches). |
| Contacts | /v1/users (people with a login) and /v1/contacts |
|
| Vendors | /v1/vendors |
|
| Vehicle assignments | /v1/vehicle_assignments |
|
| Meter entries | /v1/meter_entries |
Voids instead of deletes. |
| Fuel entries | /v1/fuel_logs |
quantity × unit_price; also VAT / eTIMS, payment method and accounting dimensions. |
| — | /v1/ev_charging_sessions |
|
| Expense entries, expense entry types | /v1/expenses, /v1/expense_types |
date instead of occurred_at; tax, payment and dimensions. |
| Service entries, work orders | /v1/work_orders with /line_items |
One resource for both. costs gives parts, labor, service and other subtotals; a completed work order is a cost. |
| Issues | /v1/issues |
|
| Submitted inspection forms | /v1/inspections (/v1/inspection_templates for the forms) |
|
| Service reminders | /v1/service_reminders |
|
| Vehicle renewal reminders | /v1/vehicle_renewals |
|
| Parts, part locations, part location details | /v1/parts, /v1/part_locations, /v1/inventory_levels |
|
| Inventory journal entries | /v1/inventory_transactions |
Read only. |
| Purchase orders (+ line items) | /v1/purchase_orders (line items embedded) |
Create drafts; approval and receiving happen in Fleet, as in Fleetio. |
| Location entries | /v1/vehicle_positions, /v1/vehicles/{id}/location |
|
| Comments, labels, places, equipment, contact renewals | — | Not in the API yet. |
What Fleet adds for cost integrations
Section titled “What Fleet adds for cost integrations”Fleetio gives you each kind of cost separately; you merge them and keep your own sync state. Fleet also gives you:
- One cost ledger (
/v1/cost_entries): every fuel log, charging session, completed work order line, expense, renewal, tyre and ERP bill, once, totalling what Fleet’s cost reports show. - An export queue per ERP (
/v1/cost_exports) with acknowledgements, so each cost is posted exactly once and changes or deletions after posting come back as updates or reversals. - Accounting dimensions pushed from your ERP, and period close.
- Fleet requests: spend approved in Fleet, purchased and billed in the ERP, with the outcome written back.
Start with Costs and your ERP.