Fleet Management API Documentation
The route to fleet data when no packaged integration exists.
Documentation is published with the API
This page is the public landing point. Endpoint reference, authentication and rate limits belong in versioned developer documentation rather than a marketing page, and will be linked from here rather than duplicated — a copy of an API reference on a marketing site is a copy that goes stale and misleads people.
What the API is expected to cover
- Vehicles: records, documents, assignment and lifecycle state.
- Tracking: current position, location history, geofence events.
- Trips: planning, dispatch, status and completion.
- Maintenance: work orders, schedules, service history.
- Fuel: sensor readings, refill and drop events.
- Drivers: profiles, assignments, behaviour events.
- Webhooks for event-driven integration rather than polling.
Before you build
If you are integrating a device rather than a business system, talk to the partner team first. Device feeds usually belong in the platform's ingestion layer, not bolted on through the public API — you will get better data and less maintenance.
Building something against our data?
Tell us what you need to read or write and we will tell you whether the API covers it today.