¶ Overview

Driven by the vision “Meet our consumers where they are,” the 3P Demand Engineering team enables external partners to integrate Uber ride-hailing directly into their own products and platforms. Partners can offer their users the ability to discover, book, and manage Uber rides — natively within the partner experience.

The 3P Demand Rides API provides access to Uber’s global supply network, pricing engine, and full trip lifecycle. Partners across travel, enterprise, consumer, and AI platforms use this API to bring Uber mobility to users at the moments and surfaces where they are already engaged.

¶ Integration Archetypes

Partners integrate with the 3P Demand Rides API in different ways depending on their platform type, technical capability, and desired user experience. The four supported archetypes are:

¶ API-Based

The partner’s backend calls Uber’s 3P Demand APIs directly, server-to-server, to create and manage rides programmatically on behalf of users. The partner owns and renders their own booking UI. This is the most flexible archetype, giving partners full control over the end-to-end experience while leveraging Uber’s supply, pricing, and trip management infrastructure.

¶ Embedded Web

The partner embeds an Uber-hosted web widget within their app or website. The widget renders product options, real-time fare estimates, and booking flows interactively, without the partner needing to build their own ride-booking interface. This archetype reduces integration complexity while offering a rich, Uber-consistent user experience within the partner surface.

¶ Deeplink

The partner generates a deeplink pre-populated with trip details — origin, destination, and optionally a product type — and redirects the user to the Uber app to complete the booking. This is the lightest integration path, requiring no server-side API calls. It is best suited for partners who want to surface Uber as a transport option without managing the booking lifecycle themselves.

¶ Agentic

AI agents and assistants can book Uber rides autonomously on behalf of users via Uber’s MCP (Model Context Protocol) server. This archetype enables natural language ride booking through AI interfaces — users can request a ride conversationally, and the agent handles the full booking flow end-to-end. It is designed for next-generation AI-native surfaces where traditional UI-driven flows are not the primary interaction model.

¶ Getting Started

To begin your integration, review the endpoint documentation linked in the sidebar. Use the Sandbox environment for development and testing before moving to production.

To contact us, email: hailables-3p-demand-group@uber.com