Three calls and live updates
POST /fare
Quote a fare
The same pricing engine that charges cards on the operator's own booking widget, for every vehicle class.
POST /bookings
Create a booking
Creates a Pending booking on the operator's Dispatch board. The price is always set by the server.
GET /bookings
Check a booking
Status by the operator's booking number or by your own reference, with the driver and vehicle once allocated. Only bookings your key created.
POST /requests
Cancel or change
Ask the operator to cancel or amend one of your bookings. Nothing changes until they approve; you are told by polling or webhook.
PUSH Webhook
Live updates
Prefer not to poll? The operator gives your key a web address and we POST a signed message when a booking is confirmed, a driver is allocated, arrives, picks up, completes or is cancelled.
See it work
Ask the operator for a key. Then:
curl -X POST "https://www.almightydispatch.com/api/v1/fare" \
-H "x-api-key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"pickup":"RM12 6AA","dropoff":"Heathrow Airport TW6 2GA","distance":32,"date":"2026-11-02","time":"12:00"}'{
"night": false,
"fares": [
{ "vehicleClassId": "4f5f1045-…", "name": "Saloon", "seats": 4, "total": 118.4,
"breakdown": [ { "label": "32 mi x 1x", "amount": 110.4 }, { "label": "Heathrow Drop-off", "amount": 8 } ] }
]
}Built to be safe to connect
✓Key in a header, never in a URL
URLs end up in logs and browser history. Yours travels only in the Authorization or x-api-key header.
✓One key per partner, one operator per key
A key can only ever touch the operator that issued it, and the operator can revoke it in one click.
✓The server sets the price
You send the journey, never a fare. A quote equals what the operator charges, and a booking cannot be made cheaper than the route allows.
✓Safe retries
Send your own reference with each booking. Send it twice and you get the first booking back, never a duplicate.
✓Rate limits
120 requests a minute and 60 new bookings an hour per key, with a Retry-After header when you reach them.
✓You only see your own bookings
A key can look up the bookings it created and nothing else. Driver fares are never returned, and the driver's phone number is sent only if the operator turns it on.
✓Test keys
A sandbox key makes simulated bookings that move through the whole lifecycle in four minutes, with webhooks, and creates nothing real on the operator's board.
✓Signed webhooks
Every push carries an HMAC-SHA256 signature you verify with a secret only you and the operator hold. https only, retried with backoff, never to private networks.
What it does not do yet
Bookings arrive as Pending and the operator confirms them, so a cancel or change you ask for waits for the operator to approve it, and there is no live GPS position of the driver (you get first name, car and registration). Build and test against a sandbox key first: it creates nothing real. We would rather tell you now than surprise you later.
How to get access
Each key is issued by the operator you want to connect to, from their own Almighty Dispatch account (Settings, Integrations, Dispatch API). If you are an operator and a platform asks you for an API key, you can create one there in a few seconds and revoke it whenever you like. Questions or want something added? info@almightydispatch.com