Webhooks

Webhooks push event notifications to your own servers the moment something happens in Fleetbase — an order is dispatched, a driver location changes, a contact is created. Navigate to Developers → Webhooks to manage your endpoints.

Creating a Webhook

Click New to configure a new endpoint.

Selecting Events

The events picker groups available events by resource (e.g. Order, Driver, Vehicle). Use the search field to filter, then click individual events to add them. Selected events appear in the panel below with a remove button next to each. You can also click All events to subscribe to every event in one step, or Clear to remove all selections.

Events available depend on which extensions are installed on your instance.

Webhook Table

Webhook Detail View

Click any webhook URL to open its detail page.

The detail view has three panels:

Metrics

A summary of delivery health — total attempts, successful deliveries, and failures. Use this to get a quick sense of whether your endpoint is receiving events reliably.

Details

The full configuration of the webhook — URL, description, API credential, API version, and subscribed events. Click Update to edit any field.

Attempts

A delivery log showing every time Fleetbase sent a request to this endpoint. Each entry shows the event that fired, the response status code, and a timestamp.

Use the attempts log to debug failed deliveries — a 5xx response or no response means your endpoint is down or misconfigured.

Enabling and Disabling a Webhook

From the detail page, use the Disable / Enable button in the header to pause or resume delivery without deleting the endpoint. Disabled webhooks remain in the list but receive no traffic.

Deleting a Webhook

Use the Delete button on the detail page or ⋯ → Delete from the list. Deleting removes the endpoint permanently along with its delivery history.

Payload Format

Fleetbase sends an HTTP POST to your endpoint with a JSON body for each event.

{
  "id": "evt_01HXYZ",
  "event": "order.dispatched",
  "api_version": "v1",
  "created_at": "2026-04-29T10:30:00Z",
  "data": {
    "id": "order_01HABC",
    "public_id": "ORD-1001",
    "status": "dispatched"
  }
}

Best Practices

• Respond quickly — return a 2xx status within a few seconds. For slow processing, acknowledge immediately and handle the payload asynchronously.
• Handle retries — Fleetbase retries failed deliveries. Make your endpoint idempotent so the same event processed twice does not cause duplicate side effects.
• Use HTTPS — always serve your endpoint over HTTPS to protect payload data in transit.