Every part of Fleetbase is built on the same API, SDKs, and extension framework we ship to you. Build custom dispatch flows, integrate with your ERP, embed live tracking in your storefront, or ship a full vertical extension to the marketplace — all on infrastructure you can self-host.
REST
Full JSON:API
WS
SocketCluster channels
50+
API endpoints
AGPL
Open source
Pick what you need. Use the REST API for clean integrations. Drop in an SDK for first-class language ergonomics. Subscribe to webhooks for event-driven workflows. Open a real-time channel for live tracking. Or build an entire vertical extension that ships through the marketplace.
Endpoint-level API reference, CLI manuals, full extension development guides, and a Postman collection you can fork in one click. All open, all maintained.
Endpoint-by-endpoint reference for the entire REST API.
Read docsScaffold extensions, manage installations, and publish to the registry.
Read docsBuild full-stack extensions — engines, packages, schemas, and publishing.
Read docsGuides, tutorials, and references for every module of Fleetbase.
Read docsEvery line of Fleetbase — the API, the console, the driver app, the SDKs, the CLI — lives on GitHub under AGPL-3.0. Self-host it, fork it, audit it, contribute to it. No black boxes, no vendor lock-in.
The questions we hear most from teams evaluating the platform.
Yes — the Fleetbase REST API is available on every plan, including the free self-hosted version. Cloud customers operate under the resource-unit allocation of their plan; self-hosted customers have no API limits beyond their own infrastructure capacity.
Bearer token authentication with per-key scopes. Generate API keys in the Developer Console, attach granular permissions, and rotate them at any time. Storefront customer-facing endpoints use a separate public-key flow.
JavaScript / TypeScript (Node and browser) and PHP have official SDKs. Storefront also ships with a dedicated JavaScript SDK. Because the underlying API is JSON-based REST, any language with an HTTP client can integrate cleanly.
Extensions are full-stack modules — an Ember Engine frontend paired with a Laravel package backend. They install with one command via the Fleetbase CLI, contribute new screens and APIs to the console, and can be published to the public registry for distribution or sale.
Yes. Fleetbase is AGPL-3.0 open source. Run the API server on your own infrastructure with full control over data residency, scaling, and customization. The same SDKs, webhooks, and extension framework work against your self-hosted instance.
Yes — the Cloud free trial includes 50 resource units against a live test environment. For self-hosted, the development setup runs locally via Docker Compose or the CLI, with seed data for immediate experimentation.
Every webhook payload is signed with an HMAC-SHA256 signature using a per-endpoint secret. The signature is included in the request headers; verify it on your end to confirm the request originated from Fleetbase.
The full Fleetbase platform lives at github.com/fleetbase/fleetbase. All modules, SDKs, mobile apps, and the CLI are in public repositories under the @fleetbase GitHub organization.
Generate an API key, send your first request, and ship a real integration before lunch. Or fork the repo and run the whole stack on your laptop.
