This guide covers the essential concepts and initial setup for building an Uber Eats Marketplace API integration. For additional use-cases outside of order fulfillment, please ensure you have an aligned business agreement with Uber ahead of beginning development.

¶ Overview

Uber Eats integrations connect your system or platform with Uber Eats for:

• Store Management - Online/offline status, hours, settings
• Menu Synchronization - Items, pricing, availability, categories
• Order Processing - Receiving, accepting, and fulfilling orders

¶ Prerequisites

Before beginning development:

• Developer Account - Start with a Sandbox applications, see Sandbox & Testing for detailed environment configuration.
• Legal Requirements - Complete NDA and API licensing agreement
• Partner Approval - Speak with your Uber Eats partner manager

¶ Core Integration Areas

Your Uber Eats integration handles four essential areas. Each area has both conceptual foundations and specific implementation requirements:

¶ 1. Authentication & Authorization

What it does: Secures all API access using OAuth 2.0 with scoped permissions.

How it works:

1. Exchange client credentials for access tokens (30-day expiration)
2. Include bearer tokens in all API request headers
3. Use separate credentials for test vs production environments

→ Implementation guide: Authentication

¶ 2. Store Management

What it does: Stores are merchant locations that receive orders and define your integration’s operational foundation.

Key capabilities:

• Status Control - Toggle stores online/offline programmatically
• Hours Management - Set regular hours and holiday schedules
• Configuration - Store-specific settings and operational parameters

How it works: Each store represents a merchant location that can receive orders. Your integration controls when stores appear available to customers and manages their operational parameters.

→ Implementation guide: Store Integration

¶ 3. Menu Synchronization

What it does: Menus define what customers can order using a hierarchical structure: Categories → Items → Modifiers.

Key capabilities:

• Full Menu Upload - Complete menu replacement via PUT requests
• Partial Updates - Update specific items, pricing, or availability
• Real-time Changes - Inventory updates, seasonal items, price changes

How it works: Your system uploads and maintains menu structures that customers see in the Uber Eats app. Changes propagate to customers in real-time, enabling dynamic pricing and availability management.

→ Implementation guide: Menu Integration

¶ 4. Order Processing

What it does: Orders flow from customers through Uber Eats to your integration via webhooks for the complete fulfillment lifecycle.

Key capabilities:

• Order Reception - Receive new orders via webhook notifications
• Order Management - Accept, deny, or modify orders as needed
• Status Updates - Communicate preparation and delivery status
• BYOC Support - Bring Your Own Courier for delivery management

How it works: Customers place orders through Uber Eats, triggering webhooks to your system. Your integration handles the complete order lifecycle from acceptance through fulfillment.

→ Implementation guide: Order Integration

---

¶ Testing Your Integration

Environment Setup

1. Create a TESTING application for safe development
2. Use sandbox domains (test-api.uber.com, sandbox-auth.uber.com)
3. Test with simulated stores and orders - no real merchant impact

Validation Steps

• Authentication - Verify token generation and API access
• Store Operations - Test status changes and configuration
• Menu Management - Upload menus and verify consumer visibility
• Order Handling - Receive webhooks and process order lifecycle

→ Technical setup details: Sandbox & Testing

---

¶ Development Resources

¶ Essential Tools

Tool	Purpose	Use Case
Developer Dashboard	Application management	Create apps, manage credentials, configure scopes
Postman Collection	API testing	Pre-built requests for all endpoints
Webhook Testing Tools	Webhook development	Local tunnel setup, payload validation

¶ Documentation Resources

Implementation Guides

• Store Integration - Merchant onboarding and management
• Menu Integration - Menu structure and synchronization
• Order Integration - Order processing and fulfillment
• Authentication - OAuth 2.0 implementation details

Technical References

• Sandbox & Testing - Environment configuration and troubleshooting
• Going Live Guide - Production launch requirements

¶ Support Channels

Technical Support

• Integration Tech Support - Technical questions and issues
• API Change Log - Stay current with platform updates
• Quality & Performance Standards - Performance requirements and best practices

¶ Next Steps

Now that you understand the core concepts, choose your path forward:

¶ For Hands-On Development

Start Building Immediately

• Sandbox & Testing - Set up your development environment
• Authentication - Implement OAuth 2.0 flow
• Store Integration - Connect your first merchant location

¶ For Project Planning

Plan Your Integration Timeline

• Quality & Performance Standards - Performance requirements and best practices
• Going Live Guide - Production launch requirements

¶ For Technical Deep Dives

Understand Complex Scenarios

• Menu Integration - Complex menu structures and updates
• Order Integration - Advanced order processing workflows
• Webhooks Guide - Reliable event handling and retry logic

---

You’re Ready To:

• Create your first sandbox application
• Understand the integration architecture
• Navigate to the right technical guides for implementation
• Plan your integration project timeline with your Uber Business and Technical Representatives

Need Help? Use Integration Tech Support for technical questions or guidance on your specific use case.