Introducing AI ModeSee how →
OrderOut
Create Account
Integration API

The API for connecting third-party delivery orders into restaurant POS systems.

REST + Webhooks. Idempotent. Built for POS companies, delivery platforms, online ordering apps, and restaurant tech companies.

Request API Key Read Docs
POST /v1/orders.accept js 
// receive a delivery order, route to POS
const order = await orderout.orders.accept({
  source:     "ubereats",
  externalId: "uber_abc123",
  store:      "store_8af2...",
  routeTo:    "clover_pos",
  items:      [...],
  options:    { autoPrint: true }
});

// → routed · printed · webhook delivered
return order.id;
What it does

One contract for supported channels and POS systems.

Normalizes every channel to one schema

Uber Eats, DoorDash, Grubhub, ChowNow, Wix — different webhooks, different fields, different formats. We map all of them to a single canonical order shape.

Routes orders into any supported POS

Clover and Square today; Toast coming soon — plus more via the adapter contract. One call into orders.accept handles routing, modifiers, and kitchen printing.

Pushes menus & availability bidirectionally

Mark an item unavailable on the POS and we propagate to every channel. Push a marketplace-side override and we keep your POS in sync.

Webhooks for every state change

Subscribe once. Receive signed, retried, replayable events for every order, refund, menu update, channel pause, or delivery state.

Built for

Teams shipping in restaurant tech.

POS Companies

Add third-party delivery to your POS.

Embed Orders + Menus + Webhooks in your existing merchant portal. White-label end-to-end.

Delivery Platforms

Reach POS without building each one.

One integration covers Clover and Square (Toast coming soon) and beyond. Single contract, single SLA.

Online Ordering Apps

Push direct orders into POS too.

Same API any marketplace uses. Your own ordering flow lands in the merchant's POS like any other channel.

Restaurant Tech

Build above the order layer.

Inventory, scheduling, accounting, analytics — pull live order data and push availability changes.

Core flows

Five resources cover most integrations.

REST

Orders

Accept, refund, cancel, reconcile.

POST orders.accept
POST orders.refund
GET orders.list
REST

Menus

Items, prices, modifiers, availability.

PUT menus.sync
POST items.unavailable
POST items.match
REST

Restaurants & Accounts

Provision locations, link POS, scope tokens.

POST restaurants.create
POST pos.link
POST tokens.create
EVENTS

Webhooks

Signed, retried, replayable 7-day log.

order.accepted
menu.synced
channel.paused
REST

Delivery dispatch

Quote and book courier marketplaces.

POST delivery.quote
POST delivery.dispatch
GET delivery.track
Examples

Real channel × POS routes.

Uber Eats
Clover

Common route. Uber Eats orders land in Clover with modifiers, kitchen printing, and sales-report attribution.

routeTo: "clover_pos"
DoorDash
Square

DoorDash orders land in Square as standard tickets — counted in daily sales, inventory, and reporting.

routeTo: "square_pos"
Grubhub
Clover

Grubhub orders push to Clover with full modifier mapping and dual-pricing (delivery vs. dine-in) support.

routeTo: "clover_pos"
Pricing

Custom pricing for integrators.

Built around your shape of integration.

API access is provided after an introductory review and approval. Pricing is tailored to your expected volume, integration depth, and white-label requirements — no public price card.

Request API Key View pricing page
API Access Start your integration
Production API Custom pricing
Enterprise / Platform Custom contract

This API powers the 3rd-Party Order Engine — connect cells like Uber Eats → Clover, DoorDash → Square, and Grubhub → Clover. More on POS integration software and the multi-marketplace integration API.

Request API access. Start building after approval.

Review the documentation, request API access, and work with our team to test your integration before going live.

Request API Key Read Docs
FAQ

Common questions.

What can I build with the Integration API?
The Integration API gives you programmatic access to OrderOut's delivery-to-POS infrastructure. You can route third-party delivery orders from Uber Eats, DoorDash, Grubhub, ChowNow, and Wix into the POS or system of your choice as standard orders, sync menus, prices, and item availability back out to those marketplaces, manage virtual brands, and pull order and reporting data — all through a single API instead of building and maintaining a separate connection to each marketplace.
Do I have to build and maintain a separate integration for each delivery marketplace?
No. You integrate once with the OrderOut Integration API and we handle the connection to each delivery marketplace for you. When Uber Eats, DoorDash, Grubhub, or another platform changes their API, we maintain and update the integration on our side — so your team isn't rebuilding or maintaining a separate connection for every marketplace.
How long does it take to integrate and go live?
Most teams integrate and go live in days. Once your API key is active you build against a single set of OrderOut endpoints, so there's no need to get approved by and integrate with each delivery marketplace individually — which is what usually stretches these projects into months.
How do I get an API key?
You can get your API key by completing an initial intro call. During that call, we'll learn more about your use case, confirm that the integration is a good fit, and walk you through the next steps. Once approved and the required prepaid integration credit fee has been paid, we'll issue and activate your API key so your team can begin testing against the OrderOut endpoints.
I already have an AI phone-ordering vendor. Can it push orders into my POS through OrderOut?
Yes. An existing AI phone-ordering service can connect to OrderOut as a channel and push its orders into the POS systems we integrate with — Clover, Square, Pecan, and more — using the OrderOut API. You keep your voice agent; OrderOut handles the POS routing.
Is there one API for POS, delivery, menus, and webhooks?
Yes. The OrderOut Integration API normalizes orders from Uber Eats, DoorDash, Grubhub, ChowNow, and Wix into one schema and routes them into Clover and Square (Toast coming soon), with menu sync, signed webhooks, and multi-courier delivery dispatch.
Can I integrate DoorDash, Uber Eats, and Grubhub through one API?
Yes. Instead of building a separate integration per marketplace, you integrate once with OrderOut and receive normalized orders from every supported channel.
How do I get API access and begin testing?
API access begins with an introductory call to review your use case and confirm that the integration is a good fit. Once approved and the required prepaid integration credit has been paid, your API key will be issued so your team can begin testing.