Uber Eats
Use Uber Eats data APIs through OpenAny to inspect store information, menu categories, dishes, prices and item options. Choose source-page URL, record identifier and coordinates as optional query conditions to select the source records or view required for your request. Use these results to compare listed dishes, prices and options when preparing a menu display for the selected establishment. Each API page provides supported parameters, request and response examples, and usage pricing.
- Endpoints
- 1In this collection
- Providers
- 1Unique providers
- Requests
- —Loading...
- Success rate
- —Loading...
- Response P50
- —Loading...
Available APIs
Common questions
How are Uber Eats APIs priced?
Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.
How do I authenticate Uber Eats requests?
Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.
Are all implementations interchangeable?
No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.
Use Uber Eats with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.