Delivery API
One integration. Every delivery marketplace.
Dispatch your own customer deliveries through Uber Direct, DoorDash Drive, Relay, and Ally — picked automatically by price + ETA on each order. When a provider fails, the next bidder takes the run. You never see it.
Live auction · #ord_8f2a1c
2.4 mi · 18 min ago
UD
Uber Direct
12 min
$8.40
DD
DoorDash Drive
9 min
$6.85WINNER
Auction settled in milliseconds You saved $1.55
Coverage
National coverage. No contracts with any of them.
We hold the marketplace relationships. You hold one bill, one dashboard, one API key.
Uber Direct Coverage · 95% US Median ETA · 24 min Avg cost · $7.80
DoorDash Drive Coverage · 94% US Median ETA · 22 min Avg cost · $7.40
Grubhub-Fulfilled Coverage · Nationwide Median ETA · — Avg cost · —
Relay Coverage · NYC + 12 metros Median ETA · 28 min Avg cost · $6.95
Ally Coverage · Tier-2 cities Median ETA · 31 min Avg cost · $8.10
What you get
Advanced delivery routing, already built. One API call.
$
Best-price routing
Every order auctions in <200ms. We pick lowest cost within your ETA tolerance — or override the logic per restaurant.
↻
Automatic failover
Driver cancels? Provider's down? We re-dispatch to the next bidder before your customer notices.
⌖
White-label tracking
Customers see your brand at every step — order confirmed, driver assigned, en route, delivered. Not theirs.
⊟
One reconciled bill
Monthly invoice across every provider. CSV export for Quickbooks. Receipt-level detail for every leg.
⌥
Refunds + disputes
Late, lost, or wrong order? File once — we chase the marketplace and credit back the delivery fee and driver tip automatically.
⌘
Bring your own drivers
Run your in-house fleet first, fall back to marketplaces when they’re busy. One dispatch board, one billing.
Start dispatching this week.
Sign up in 4 minutes. No contracts with the marketplaces. Pay per delivery.
Questions
What is the Delivery API? +
The Delivery API lets you dispatch couriers from delivery providers using a single endpoint — for ordering platforms, third-party tools, or restaurant tech that needs delivery without contracting each provider directly.
How is the Delivery API priced? +
Delivery API pricing is customized based on your expected delivery volume and integration needs. Request API access to review your use case, pricing, and onboarding requirements with our team.
Do I have to integrate each delivery provider's own API, like DoorDash's or Uber Eats', myself? +
No. With the Delivery API you dispatch couriers through one OrderOut endpoint instead of setting up and maintaining a separate developer integration with each delivery provider. OrderOut keeps the provider connections behind that single endpoint, so your team builds against one interface rather than tracking each provider on its own.
Can I add delivery to my own ordering platform or POS with the Delivery API? +
Yes. The Delivery API is built to add courier dispatch inside your existing product — an ordering platform, third-party tool, or POS — by calling a single OrderOut endpoint to request a delivery. Delivery becomes a feature of your own product instead of a set of separate provider integrations to build and maintain.
Can I get delivery status or tracking through the Delivery API? +
Delivery requests are made through the single OrderOut endpoint, and the delivery-status and tracking details available for your integration are confirmed during onboarding. Request API access to review the exact status and webhook capabilities for your use case with the OrderOut team.
Is the Delivery API the same as connecting DoorDash or Uber Eats orders? +
No — those are different OrderOut products. The Delivery API dispatches couriers from delivery providers through one endpoint so you can offer delivery. Routing marketplace orders from Uber Eats, DoorDash, Grubhub, ChowNow, or Wix into a POS is the Integration API. Teams often use them together — one to bring orders in, the other to get deliveries out.
How do developers get started with the Delivery API and its documentation? +
Access to the Delivery API starts with a short intro call to review your delivery volume, use case, and integration needs. Once your use case is confirmed, your team is set up to build against the OrderOut endpoints, and the integration details and endpoints are shared as part of that onboarding.
