For developers | Orkestro
For developers

One call. Every quote.

Two APIs, one network: the Partner API pushes orders in and manages merchants; the Fleet API plugs your fleet into the marketplace. Setup takes most teams an afternoon.

Read the API docs

Sits between your stack and every fleet.

Orders flow in from your storefront, POS or marketplace, and out to every courier fleet on the network.

Shopify logo storekit logo Flipdish logo HubRise logo Zapiet logo Spoonfed logo SevenRooms logo

Something else in your stack? Build it on the REST API →

The request

One order in. Every fleet considered.

Send pickup, dropoff and your rules, the response carries every fleet's quote, the dispatch decision, the backup and a white-label tracking URL.

Read the API docs →

POST /orders Representative example, see docs
{
  "pickup":  { "contact": { "name": "Brindle Bakery Soho" },
               "address": "1 Example Street, London EC1A 1AA" },
  "dropoff": { "contact": { "name": "A. Khan" },
               "address": "2 Example Road, London N1 1AA" },
  "parcel":  { "items": 2, "reference": "web-48211",
               "handlingInstructions": "keep flat" },
  "schedule": { "type": "urgent" },
  "callbackUrl": "https://your-platform.com/webhooks/orkestro"
}

// 201 Created
{ "orderId": "1f4a2c9e-…" }   // deliveries, quotes and status
                            // arrive on your callbackUrl

Everything the portal does, over REST.

Partner API, for merchants & platforms

Create & cancel orders

POST /orders with pickup, dropoff, parcel and schedule, urgent, scheduled windows, or predicted pickup. Async cancel with fee rules.

In the docs

Quote requests

POST /v1/quote-request with optional fleet, vehicle and service filters; valid quotes arrive on your callback, accept within 15 minutes.

In the docs

Callbacks

Status and location updates, chat messages, final settled price, geocoding errors and PIN-code verification, pushed to your callbackUrl.

In the docs

Merchant management

POST /v1/merchants creates stores under your platform, each with its own API key and routing rules.

In the docs
Fleet API, for couriers joining the network

Quote & accept bookings

Implement request-quote, accept-booking and cancel-booking on your server, Orkestro sends candidate jobs, you answer with a price and a supplier reference.

In the docs

Status & location updates

One endpoint reports the whole lifecycle, driver assigned, at pickup, in transit, delivered with proof, with location pings at least every 60 s.

In the docs

Label upload

Push printable PDF labels per booking for national-courier and fulfilment-hub work.

In the docs

Onfleet integration

Already on Onfleet? Connect your account instead of building endpoints, jobs appear as linked tasks and re-offer after 30 minutes unassigned.

In the docs
The order never dies, on the wire

A failure is just another event.

When a courier stalls, the rescue happens network-side, your integration just receives the events. No polling, no special-case code.

webhook · delivery.events Representative example, see docs
{ "orderId": "1f4a2c9e-…", "status": "driver_assigned",
  "fleet": "nimbus", "eta": "2026-07-24T18:22:00Z" }

{ "orderId": "1f4a2c9e-…", "status": "driver_reassigned",
  "fleet": "kestrel" }   // backup fleet, same tracking URL

{ "orderId": "1f4a2c9e-…", "status": "success",
  "proofOfDelivery": "pod_Xf91Ab" }
Keep reading
Marketplace

One integration, quotes from every fleet on the network.

Open Marketplace →
Fleet partners

How fleets join the network and earn volume.

Open Fleet partners →

See how it works →