Uber Eats exposes a family of developer APIs through the Uber Developer Portal that let restaurants, marketplace platforms, POS providers, and logistics partners integrate directly with Uber Eats and Uber Direct. The Uber Eats Marketplace APIs cover store onboarding, store status and hours, menu management, order ingestion and fulfillment, delivery fulfillment (Uber-courier and BYOC), promotions, and reporting. Uber Direct (Deliveries) exposes Uber's courier network for on-demand same-day delivery — quotes, deliveries, courier tracking, proof of delivery, refunds, pick-and-pack, and webhook notifications. All APIs are RESTful, JSON, and gated by OAuth 2.0 client credentials issued from the Uber Developer Portal.
Uber Eats publishes 15 API contracts indexed on the APIs.io network, including Customers API, and 14 more. Tagged areas include Uber Eats, Uber Direct, Food Delivery, Last Mile Delivery, and Restaurant.
The Uber Eats catalog on APIs.io includes 2 JSON-LD contexts and 2 Spectral governance rulesets.
Uber Eats’ developer surface includes authentication, documentation, engineering blog, status page, and 19 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/uber-eats/"><img src="https://apis.io/badge/uber-eats/card.svg" alt="Uber Eats on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Access Clarityscores 18.4 — up to +16.3 composite points
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
The Integration Activation API suite onboards merchant stores onto a partner's Uber Eats integration, connecting Uber store identifiers to a partner platform and enabling subseq...
The Menu API suite lets integrations retrieve and upsert full menus for a store and update individual menu items, modifier groups, prices, suspensions, and availability windows.
The Order API suite handles inbound Uber Eats orders, including order accept/deny, status updates, item-level adjustments, and cancellation flows. Orders are typically delivered...
The Delivery Partner API suite handles delivery fulfillment by Uber couriers for Uber Eats orders, including courier assignment, tracking, and status updates surfaced back to th...
The Delivery BYOC ("Bring Your Own Courier") API suite supports merchants and marketplace partners that use their own delivery fleet, exchanging assignment, status, and proof-of...
The Promotions API suite creates and manages marketing campaigns and discounts on Uber Eats stores, including campaign lifecycle, targeting, and reporting.
The Reporting API suite returns transactional, financial, and performance reports for Uber Eats stores, used by merchants and marketplace partners for reconciliation and analytics.
The Organizations API lets Uber Direct partners manage parent organizations and child accounts (e.g. multi-tenant merchants), including provisioning of API credentials and store...
The Courier Pick & Pack API supports shop-and-pay style deliveries where the courier shops on behalf of the customer, including item lists, substitutions, and shopping progress ...
The Refund API supports refund requests on completed Uber Direct deliveries, including the corresponding webhook events that notify merchants of refund outcomes.
Both Uber Eats and Uber Direct send webhook events for order lifecycle, courier updates, refunds, shopping progress, and delivery status. Partners register webhook URLs in the U...
Uber APIs are authenticated using OAuth 2.0. Server-to-server integrations use the client_credentials grant; user-facing integrations use the authorization_code grant with PKCE....
Not yet checked against Uber Eats's own pricing page. Compiled by API Evangelist on 2026-05-22; confirm before you rely on a figure. A free plan or tier is listed.
Plan
Price
Developer API Access free
Free
Marketplace Lite commission
$20 per marketplace Commission
Marketplace Plus commission
$25 per marketplace Commission · $30 per uber One Member Commission
Marketplace Premium commission
$30 per marketplace Commission
Pickup commission
$7 per pickup Commission (Validated Pricing) · $10 per pickup Commission (Standard)
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.