Uber
Uber is a global technology platform offering transportation, food delivery, and logistics services. Its developer platform provides APIs for integrating ride requests, food ordering, on-demand delivery, voucher programs, and business travel management into third-party applications. APIs use OAuth 2.0 authentication with scope-based access controls and support both production and sandbox environments.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Uber the way a machine reads it — 132 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Uber scores 49.5/100 (developing), with a separate agent-readiness read of 23/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Uber's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/uber/"
title="Uber on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/uber.svg"
alt="Uber Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/uber/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/uber/"
title="Uber on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/uber/card.svg"
alt="Uber Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Uber
Each block below is one kind of artifact we hold for Uber. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Uber Guest Rides API
The Uber Guest Rides API enables businesses to allow their users to request rides from Uber without requiring an Uber account. Uses OAuth 2.0 with the guest.rides scope for auth...
Uber Codes API
Voucher code generation and distribution
Uber Deliveries API
Delivery creation and management
Uber Estimates API
Price and time estimates for rides
Uber Locations API
Business location management
Uber Menus API
Menu items, modifiers, and pricing
Uber Orders API
Eats order receipts
Uber Organizations API
Organization and account management
Uber Partners API
Driver partner profile and activity data
Uber Places API
Saved rider locations
Uber Products API
Uber product types available at a location
Uber Programs API
Voucher program management
Uber Redemption API
Voucher code redemption
Uber Refunds API
Delivery refund processing
Uber Reporting API
Analytics and performance metrics
Uber Requests API
Ride request management
Uber Riders API
Rider profile and history
Uber Stores API
Store management and operational status
Uber Templates API
Voucher program templates
Uber Trips API
Business trip receipts and invoices
Scroll within the panel for all 20 ·
Postman Collections 19
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Uber for Business Codes API
POSTMANScroll within the panel for all 19 ·
Open Collections 26
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONUber for Business API
OPEN COLLECTIONUber for Business Codes API
OPEN COLLECTIONUber for Business Codes Deliveries API
OPEN COLLECTIONUber Direct API
OPEN COLLECTIONUber Drivers API
OPEN COLLECTIONUber Eats API
OPEN COLLECTIONUber for Business Codes Estimates API
OPEN COLLECTIONUber for Business Codes Locations API
OPEN COLLECTIONUber for Business Codes Menus API
OPEN COLLECTIONUber for Business Codes Orders API
OPEN COLLECTIONUber for Business Codes Organizations API
OPEN COLLECTIONUber for Business Codes Partners API
OPEN COLLECTIONUber for Business Codes Places API
OPEN COLLECTIONUber for Business Codes Products API
OPEN COLLECTIONUber for Business Codes Programs API
OPEN COLLECTIONUber for Business Codes Redemption API
OPEN COLLECTIONUber for Business Codes Refunds API
OPEN COLLECTIONUber for Business Codes Reporting API
OPEN COLLECTIONUber for Business Codes Requests API
OPEN COLLECTIONUber for Business Codes Riders API
OPEN COLLECTIONUber Riders API
OPEN COLLECTIONUber for Business Codes Stores API
OPEN COLLECTIONUber for Business Codes Templates API
OPEN COLLECTIONUber for Business Codes Trips API
OPEN COLLECTIONUber Vouchers API
OPEN COLLECTIONScroll within the panel for all 26 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Uber GraphQL Schema
This conceptual GraphQL schema covers the full breadth of the Uber developer platform, spanning ride-sharing (Riders API, Drivers API, Guest Rides), food delivery (Uber Eats), o...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Uber Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Uber Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Uber Finops
FINOPSFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
OAuth 2.0 Authorization
All Uber developer APIs authenticate with OAuth 2.0 bearer tokens using scope-based access controls for both client-credentials (server-to-server) and authorization-code (on beh...
Sandbox Environment
Most APIs offer a sandbox for simulating rides, deliveries, and orders without dispatching real couriers or charging real payment methods.
Webhooks
Uber Direct and Uber Eats publish real-time event webhooks for delivery status, courier updates, shopping progress, refunds, and order lifecycle changes.
Courier Delivery Network
Uber Direct exposes Uber's on-demand courier network so merchants can quote, create, track, and manage last-mile deliveries from their own storefronts.
Marketplace Integration
Uber Eats Marketplace APIs let restaurants and POS partners synchronize stores, menus, and orders with the Uber Eats consumer marketplace in real time.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Uber Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Uber API Rules
SPECTRALUber API Rules
SPECTRALJSON Schema 39
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Activities
JSON SCHEMABusinessLocation
JSON SCHEMABusinessLocationRequest
JSON SCHEMAUber Direct Delivery
JSON SCHEMADeliveryQuote
JSON SCHEMADeliveryRequest
JSON SCHEMADriverProfile
JSON SCHEMADriverTrip
JSON SCHEMAMenu
JSON SCHEMAMenuCategory
JSON SCHEMAMenuItem
JSON SCHEMAOrder
JSON SCHEMAOrderReceipt
JSON SCHEMAOrganization
JSON SCHEMAPayment
JSON SCHEMAPaymentsResponse
JSON SCHEMAPlace
JSON SCHEMAPlaceUpdate
JSON SCHEMAPriceEstimate
JSON SCHEMAProduct
JSON SCHEMAReceipt
JSON SCHEMARefund
JSON SCHEMARefundRequest
JSON SCHEMAReportRequest
JSON SCHEMAUber Ride Request
JSON SCHEMARideDetails
JSON SCHEMARideEstimate
JSON SCHEMARideRequest
JSON SCHEMARiderProfile
JSON SCHEMAStore
JSON SCHEMAStoreUpdate
JSON SCHEMATimeEstimate
JSON SCHEMATripReceipt
JSON SCHEMATripsResponse
JSON SCHEMAVoucherCode
JSON SCHEMAVoucherProgram
JSON SCHEMAVoucherProgramRequest
JSON SCHEMAVoucherProgramUpdate
JSON SCHEMAVoucherTemplate
JSON SCHEMAScroll within the panel for all 39 ·
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Uber Riders Structure
JSON STRUCTUREUber Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Restaurant Delivery Fulfillment
Restaurants and food brands use Uber Direct to dispatch couriers for delivery of orders placed on their own websites and apps, bypassing the Uber Eats marketplace fee structure.
Menu And Order Synchronization
POS and online-ordering platforms integrate Uber Eats APIs to keep store hours, menus, pricing, and order status in sync between their systems and the Uber Eats marketplace.
Corporate Travel And Meals
Enterprises use Uber for Business and Vouchers to provision rides and meals for employees and guests with centralized billing, expense reporting, and policy controls.
Guest Ride Provisioning
Healthcare, hospitality, and service businesses use Guest Rides to request trips on behalf of customers who do not have an Uber account.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Point Of Sale Systems
Uber Eats integrates with restaurant POS platforms for automated order injection and menu management.
E-Commerce And Ordering Platforms
Uber Direct integrates with online ordering and e-commerce checkout flows to add same-day local delivery.
Expense And Travel Management
Uber for Business integrates with expense management and corporate travel platforms via receipts and invoices.
Resources
Every other property we hold for Uber — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/uber · machine-readable index on apis.io
This is an independent, third-party profile of Uber, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.