Real-Time Business Events

Don't poll. React. Keep your systems in sync with bookings, payments, and fleet movements using our event-driven architecture. We prioritize Webhooks for real-time delivery, with a Pull API for reliable recovery.

Choose your Delivery Model

Recommended

Webhooks (Push)

The Notification Dispatcher sends an HTTP POST request to your endpoint immediately when an event occurs.

Real-time delivery
Automatic Retries (Initial + 2 attempts)
Signed payload (HMAC-SHA256)
Ideal for most integration scenarios

Fallback

Pull API

Retrieve undelivered or historical events manually via a standard REST endpoint.

Partner-driven retrieval
Available if webhook delivery fails
Useful for firewalled environments
Endpoints: GET /events

Event Catalog

Events are grouped by domain. Subscribing to a domain (e.g., Bookings) enables all associated event types.

Booking

Lifecycle changes for reservations. booking_createdbooking_updatedbooking_cancelledbooking_acceptedbooking_refused

Payment

Transaction status updates. payment_pre_authorizedpayment_capturedpayment_refundedpayment_failed

Rental

Physical vehicle movements. rental_startedrental_extendedrental_closedrental_incident

Customer

Profile modifications. customer_createdcustomer_updatedcustomer_deleted

Location

Station and branch updates. location_createdlocation_updatedlocation_deleted

Anatomy of an Event

Every event, regardless of type, follows a strict standard envelope.

The resource object contains the minimal information needed to identify the impacted entity. You should use the ID provided to fetch the full details via the corresponding API (e.g., GET /bookings/{id}).

Type: Identifies the business action.
Resource: Points to the affected object.
Signature: (Header) Verifies authenticity.

// Example: Booking Accepted Event
{
  "id": "evt_8f3a7e9f",
  "type": "booking_accepted",
  "timestamp": "2025-10-22T14:31:00Z",
  "resource": {
    "type": "booking",
    "id": "BK123456"
  }
}

Security & Activation Checklist

Follow these steps to ensure a secure and reliable integration.

Security Requirements

HTTPS Required
All webhook endpoints must be served over HTTPS to ensure transit security.

Validate Signatures
Verify the X-UMP-Signature header using your secret key to prevent spoofing.

Idempotency
Log the unique evt_id to handle potential duplicate deliveries gracefully.

How to Activate

Select Events
Choose the specific event types you need from the catalog above.

Prepare Endpoint
Deploy your Webhook URL (and optionally a Pull strategy for fallback).

Request Access
Contact support to provision your subscription.

Request Activation