Introduction to Eats APIs
The Eats APIs enable partners to programmatically manage stores, menus and orders on the Uber Eats platform.
¶ Overview
Use the Store API to onboard; manage; or enumerate merchant store information and temporal store status (pausing; unpausing; and holiday hour overrides). These APIs can also be used to manage app access and integration details on a store level.
The Menu API provides the ability to manage menus as well as regular store hours.
Ingest and manage incoming orders from Uber Eats with the Order API. The API includes webhooks for incoming order notifications and cancellations from Uber Eats. Retrieve, accept, deny, and cancel orders with the Order API endpoints.
Use the Reporting API to request and access standardized reporting. The API includes a notification webhook once a report is completed.
Menu API | Reporting API |
---|---|
API Endpoints
|
API Endpoint
Webhook Notifications
|
Store Management | Order Workflow Management |
---|---|
API Endpoints
|
API Endpoints
Webhook Notifications
|
¶ Point-of-Sale (POS) Integrations
Get the most value out of the APIs by setting them up to synchronize your store menu from your store’s POS system.
Once this is set up, you can inject Eats orders straight to the POS. This eliminates the need for manual and duplicate processes between Eats and the POS, such as marking items as sold out or transposing order details from tablets.
¶ Next steps
Before starting an integration, we first suggest reviewing the following page(s):
- Versioning & Upgrade Timelines
To ensure you can accomodate our upgrade schedules and that your integration is built to be resilient to non-breaking changes. - Quality & Performance Standards
To ensure your integration is built in a way that can meet the standards and performance criteria outlined in this document.
Once you are ready, visit our Getting Started page to begin the integration process.