Uber Eats API
Uber Eats documents a proper OAuth 2.0 Marketplace API with webhooks and a self-serve test app, but production scopes are whitelisted only after an NDA, API licence agreement, partner manager sign-off and an integration review with Uber.
Frequently asked questions
Uber Eats scores D+ on Supergood's API Report Card. Uber Eats documents a proper OAuth 2.0 Marketplace API with webhooks and a self-serve test app, but production scopes are whitelisted only after an NDA, API licence agreement, partner manager sign-off and an integration review with Uber.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Uber Eats is the delivery marketplace of Uber Technologies (NYSE: UBER), launched over ten years ago and now the second-largest US food delivery platform.
Restaurants & Food Service, plus grocery, convenience, alcohol and retail. Merchants range from independents to the large restaurant groups that Uber says account for a significant share of Delivery gross bookings. Restaurants keep menus, hours, photos and store status current in Uber Eats Manager, accept and prepare orders on the Orders tablet or POS, download payment, order history, inaccurate-order and feedback reports (up to 31 days at a time), and manage refunds and disputes.
Over 1.5 million merchant partners worldwide (Uber Eats Merchant Impact Report), about 26.1 percent of US food delivery sales at the end of 2024 per Earnest Analytics, and a Delivery business above a $100 billion annual gross bookings run-rate.
Store profiles and hours, menus and prices, orders with customer names and delivery details (PII), courier status, payouts, fees and invoices, inaccurate-order and refund data, customer and item ratings and comments, downtime and marketing spend. Card data stays with Uber.
Uber Eats launched in the mid 2010s; the Marketplace API has been public for several years and the docs were reorganized recently into guides (getting started, authentication, sandbox and testing, going live, quality and performance) plus a per-endpoint reference.
A POS developer could not generate a client credentials token because no scopes were selectable in the dashboard; the accepted answer was to contact whoever provisioned the account. Developers report the dashboard offers no way to select Eats scopes, so calls fail with "This endpoint requires at least one of the following scopes", and several ask whether a legal agreement is required first. Full sourced list under Sources below.
Common alternatives include DoorDash, Grubhub, Olo, Toast, Instacart. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official Uber Eats MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Uber Eats doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.