All Features
Developer Tools

Public API

Every piece of data in Fleetbooks is accessible through a documented RESTful API. Pull live vehicle positions, query historical trips, manage geofences, or receive event notifications via webhooks — 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
Webhooks
Real-time event push
API key + OAuth
Authentication options
Fleetbooks API documentation

Available endpoints

A selection of the resources accessible through the Fleetbooks API.

MethodEndpoint
GET/vehicles
GET/vehicles/:id/position
GET/trips
GET/trips/:id
GET/drivers
GET/alerts
POST/geofences
POST/webhooks

Authentication

API access is authenticated with API keys scoped to specific read or write permissions. Keys are issued per account and can be rotated or revoked at any time from the settings panel.

OAuth 2.0 client credentials flow is available for server-to-server integrations where you need tokens with a defined expiry rather than long-lived keys.

Example request header

Authorization: Bearer YOUR_API_KEY

Real-Time Webhooks

Subscribe to any event type and receive an HTTP POST to your endpoint within seconds. Each payload includes the event type, timestamp, affected resource ID, and relevant data — no polling required.

trip.started
trip.ended
geofence.entered
geofence.exited
alert.triggered
speeding.detected
harsh_braking.detected
device.offline

Key capabilities

What the Fleetbooks API does for your integrations.

Full REST API Coverage

Vehicles, trips, alerts, drivers, and geofences 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. An OpenAPI specification is available for code generation.

Rate Limiting and Quotas

API usage is subject to per-account rate limits returned in response headers. Webhook deliveries include automatic retry logic with exponential backoff.

Integration patterns

Common ways development teams use the Fleetbooks API in production.

01

ERP and TMS Integration

Feed real-time vehicle positions and completed trip records into your transport management or ERP system. Webhooks trigger job status updates the moment a trip ends, without any polling.

02

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.

03

Customer-Facing Tracking Portals

Embed live delivery tracking into your own customer portal or mobile app using the Fleetbooks API as the data layer. Your customers see tracking in your branded interface without knowing Fleetbooks is behind it.

Ready to start building?

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