Integration · Uber

Uber Direct API and Uber Eats integration for restaurant groups

Send orders from your own app to Uber couriers through the Uber Direct API, or take Uber Eats orders straight into your POS. We help you pick the right route, get access and keep it running.

Takes two minutes. An engineer reads it, and Max replies within 1 business day.

API
REST, OAuth 2, signed webhooks
Direct access
Self-serve, test mode first
Uber Eats access
Uber's written approval
Markets
US, Canada, UK

In short

The Uber Direct API connects your own app or website to Uber couriers: quote, create, track and cancel deliveries, with status by webhook. Access is self-serve with a test mode. Uber recommends the API above 1,000 deliveries a month; below that, its dashboard or a POS partner is enough. Uber Eats is a separate API that brings marketplace orders into your POS and syncs menus and store status, with Uber's approval. dev.family builds both and runs them under an SLA.

What data moves

What moves through Uber Direct and Uber Eats

Read means we can get it from Uber. Write means we can send it to Uber.

ObjectReadWriteWhat the API supports
Direct: quotes and deliveriesYesYesQuote valid 15 minutes; create, update and cancel deliveries
Direct: status and courier locationYesNoWebhooks for status, courier location every 20 seconds, refunds
Direct: proof of deliveryYesPartlyProof of delivery and PIN options, set when you create the delivery
Uber Eats: ordersYesYesAccept or deny, cancel, mark fulfilled
Uber Eats: menus and storesYesYesMenu upload, hours, online status, promotions
Uber Eats: reportingYesNoReporting API for sales and payouts

Common setups

How groups connect Uber Direct and Uber Eats

  • Own app, Uber couriers

    Your appUber DirectCustomer

    Delivery from your own channel, with your prices and your guest data.

  • Uber Eats into the POS

    Uber EatsDeliverectToast

    Marketplace orders land in the POS directly or through middleware.

  • Several courier networks

    NashUber DirectDoorDash Drive

    An orchestrator picks the network per order and falls back if one fails.

API access

How Uber Direct and Uber Eats API access works

Uber offers three ways into Uber Direct: the dashboard for manual orders, a POS or ordering platform that already integrates with it, and the Uber Direct API, which Uber recommends above 1,000 deliveries a month. For the API, you sign up at direct.uber.com and get a customer ID, client ID and client secret from the dashboard. Credentials start in test mode; production needs billing details and account approval. Groups with many brands agree the customer ID setup with their Uber account manager before go-live.

Uber Eats Marketplace APIs are different: Uber says access may require its written approval, and production requires at least 99% of orders injected successfully.

Docs developer.uber.com · Direct changelog, latest entry October 28, 2026 · checked November 9, 2026

What we need from you

  • Your Uber merchant or Direct account
  • Which stores and brands to connect
  • Billing details for Direct production
  • Who signs off on go-live

Getting access:

Direct test credentials the same day; production after Uber approves the account.

Not sure what your contract allows? Send us the systems and the data you need. We'll tell you which access route fits and what the connector involves.

Get a scope estimate

Platform limits

Where Uber integrations break

  • Short quotes. A Direct quote is valid for 15 minutes. Slow checkouts have to re-quote.

  • Few webhook retries. Uber retries a webhook only on server errors and timeouts, with short backoff starting at 10 seconds, and stops after three attempts. Missed statuses have to be read back from the API.

  • 99% order injection. Uber Eats production requires at least 99% of orders injected into the POS. Every failure counts against you.

  • Three months on old versions. Deprecated Uber Eats API versions stay up for three months, then stop.

  • Sandbox limits. The Direct sandbox allows 200 requests per 10 minutes; production limits vary by endpoint.

Run

Who fixes it when the platform changes its API

  • Monitoring

    We check the connector against the live API every day and log every failed call.

  • Versions

    We track the platform's changelog and move the connector to a new version before the old one is retired.

  • Alerts

    Lost or stuck orders page the on-call engineer, who fixes them under the SLA.

Questions

Didn't find your answer? Ask on the call.

  • An Uber Direct integration sends orders from your own app or website to Uber couriers through the Uber Direct API. An Uber Eats integration brings orders from the Uber Eats marketplace into your POS and keeps your menu, hours and store status in sync there. They use different APIs and different access.

  • Sign up at direct.uber.com, where available. The dashboard gives you a customer ID, client ID and client secret, and new credentials start in test mode. Production needs billing details and account approval.

  • Uber recommends the dashboard for businesses with fewer than 1,000 deliveries a month: staff enter orders by hand, with no integration. Above 1,000 a month, Uber recommends the API, which automates order processing but needs a technical integration. A third route is a POS, OMS or ordering platform that already integrates with Uber Direct. For a group taking orders in its own app across many stores, the API is usually the right call.

  • Uber says access to the Marketplace APIs may require its written approval. Production also requires an order injection success rate of at least 99%, so the connector has to be solid before launch.

  • Uber's own developer docs put a full POS integration at four to eight weeks and an enterprise reporting integration at two to four weeks. We fix the price per scope before the build.

  • In the US, Uber advertises delivery from $7.99, depending on distance, speed, integration type and market. The UK page shows no price.

  • Uber Direct runs in the US, Canada and the UK, where Uber says it reaches more than 90% of the population. Check Ireland and other markets with Uber.

Get a scope estimate for your Uber integration

Tell us whether you need Uber couriers for your own orders, Uber Eats orders in your POS, or both. An engineer will reply with the access route and how long it takes.

a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work

Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors

Max will reply within 1 business day with what's possible, what access we need and a rough timeline.

Who are you