Developer Tools

Public API

Every piece of data in Fleetbooks is accessible through a documented RESTful API. Pull live vehicle positions, query historical journeys, manage geofences and alert rules, or generate reports — without logging into the dashboard.

Use the API to connect Fleetbooks to your existing systems, build internal dashboards with your exact metrics, or deliver tracking directly inside your own customer-facing products.

REST

API architecture

80+

Endpoints, 18 resource types

API Key

Authentication

Request API Access View Documentation

Available endpoints

A selection of the 80+ endpoints accessible through the Fleetbooks API. See the full reference for all resource types.

Method	Endpoint	Description
POST	/api/tracking/latest-positions	Get the live GPS position and speed for a set of assets
GET	/api/tracking/history	Query historical position and sensor data for an asset over a date range
POST	/api/tracking/journeys	Retrieve completed journeys with route, stops, and duration
POST	/api/assets/search	List and filter fleet assets with pagination
GET	/api/employees	List drivers with assignment status and vehicle authorisation
GET	/api/geofences	List geofences and their boundaries
POST	/api/alert-rules	Create an automated alert rule triggered by asset events or thresholds
POST	/api/reports	Generate a fleet report
GET	/api/report-schedules	List reports scheduled to run automatically
GET	/api/maintenance-logs	Query completed maintenance events for assets
GET	/api/fuel-logs	Query manual fuel fill-up entries for assets
GET	/api/telematics-devices	List telematics hardware devices assigned to assets

Authentication

Every request is authenticated with an API key issued by Fleetbooks, scoped to a specific tenant. Keys are issued per account or reseller and can be rotated or revoked by your account manager.

Requests that are missing a key, use an invalid or expired key, or exceed the account's usage limit are rejected with a 401 and a plain-text reason.

Example request headers

X-API-Key: flb_xxxxxxxxxxxx
tenant: acme-logistics

Resource Categories

The API is organised into 18 resource categories covering everything from live GPS tracking to driver management, reporting, and reference data.

Live Tracking

Asset Management

Asset Groups

Asset Sensors

Asset Analytics

Devices

Geofences

Alert Rules

Reports

Report Schedules

Fuel Logs

Maintenance Logs

Inspections

Drivers

Tags

Vehicle Makes

Vehicle Models

Asset Classes

Key capabilities

What the Fleetbooks API does for your integrations.

Full REST API Coverage

Assets, drivers, geofences, alert rules, reports, and reference data are all accessible via predictable endpoints with consistent JSON responses and standard HTTP status codes.

Comprehensive Documentation

Every endpoint is documented with request parameters, response schemas, and worked examples in an interactive reference. The full OpenAPI specification is available for code generation.

Standardised Error Responses

Errors follow the RFC 7807 Problem Details format, with a clear status code, title, and field-level validation messages so failures are easy to handle programmatically.

Integration patterns

Common ways development teams use the Fleetbooks API in production.

ERP and TMS Integration

Pull live asset positions and completed journeys into your transport management or ERP system to drive automated job status updates.

Custom Internal Dashboards

Build internal dashboards tailored to your exact business metrics — cost per kilometer, utilization by depot, or driver rankings — using live Fleetbooks data as the source without building your own data collection.

Reseller and Multi-Tenant Platforms

Manage integrations across multiple client accounts from a single set of API keys, using the tenant header to scope every request to the right account.

Ready to start building?

Request API access and we'll send you credentials and documentation to get started.

Request API Access View Docs