FleetBold Partner API
Track, unlock and command vehicles from your code
Live location, vehicle state, trips and bookings over REST, signed webhooks to your backend, and remote commands — lock, kill switch, honk, Tesla controls — on the fleets your users connect with OAuth.
- GET/v1/vehicles/{id}/location
- POST/v1/vehicles/{id}/commands
- WEBHOOKvehicle.telemetry
- AUTHOAuth 2.0 · PKCE · OIDC
Build and test with your own account and test users, go live after review. Requires a company email address.
Vehicle commands
Send a command, follow it end to end
One endpoint for every vehicle: POST /v1/vehicles/{vehicle_id}/commands. FleetBold sends it the way the FleetBold app does and answers 202 Accepted with a command resource. Results are pull-only: no command webhooks, you read GET /v1/commands/{command_id}.
Tesla: answered within the request
trunk_control_command, flash_lights_command and honk_horn_command go through the Tesla Fleet API, so the 202 already says succeeded.
Command:
# Waiting for the app to send a command…
FleetBold device: kill switch
fleetbold/engine_cut and fleetbold/engine_recover go from your app to FleetBold, from FleetBold to the device in the vehicle, and the answer comes back the same way: 202 Accepted with sent.
Command:
# Waiting for the app to send a command…
Illustration. Engine cut can disable a vehicle: follow the safety guidance in the Vehicle commands guide.
Telemetry webhooks
Realtime vehicle data, one format
The vehicle streams telemetry to FleetBold all the time. FleetBold turns each provider's fields into one vehicle.telemetry event and posts it to your endpoint, signed with X-FleetBold-Signature, as each event arrives (no per-vehicle interval). Pause or resume it per connection with PATCH /v1/connection/webhook.
Command:
# Webhook paused: waiting for the app to resume it…
Illustration. Endpoints and data groups are set in the console; forwarding starts when the user grants webhooks:receive with location:read and offline_access. See the Webhooks guide.
How it works
- 1
Create a company account
Sign up with your company email and accept the Developer Terms.
- 2
Register your app
Name, company, client type, redirect URIs and the scopes you need. Verify the contact email by link.
- 3
Build and test
Get your client id and secret, then test with your own account and test users while in development.
- 4
Go live
Submit for review. Once approved, any FleetBold user can connect your app.
Documentation
Ready to build?
Create your developer account with your company email.