Restaurant and menu price monitoring
Use UberEats endpoints to turn restaurant and menu price monitoring into repeatable API requests with documented inputs and JSON responses.
Turn public UberEats pages into structured restaurant data — search by delivery location or keyword, full store detail with menu sections and item prices, and a reviews snapshot, as normalized JSON for delivery-market and menu research. Credential-free.
Extract UberEats restaurant search, store detail, menus, and reviews — rating, cuisine, delivery estimate, and prices — as structured JSON.
Endpoint families
2
Documented params
11
Examples
3
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
7
Schema refs
3
{
"platform": "UberEats",
"endpoint": "ubereats-search",
"method": "GET",
"path": "/ubereats/search",
"auth": "apiKey"
}Use cases
Extract UberEats restaurant search, store detail, menus, and reviews — rating, cuisine, delivery estimate, and prices — as structured JSON.
Use UberEats endpoints to turn restaurant and menu price monitoring into repeatable API requests with documented inputs and JSON responses.
Use UberEats endpoints to turn delivery-market and cuisine research into repeatable API requests with documented inputs and JSON responses.
Use UberEats endpoints to turn rating and review collection into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/ubereats/store/{store_id}
/ubereats/search
Endpoint catalog
/ubereats/searchReturns restaurants delivering to a location: name, rating, review count, delivery estimate, cuisine tags, and image. Pass a keyword to search by name/cuisine/dish, or omit it to browse the general feed for that location. Credential-free public UberEats data.
/ubereats/store/{store_id}Returns a normalized UberEats store: address, phone, rating, cuisine tags, hours tagline, and the full menu (sections with items, descriptions, and prices). Credential-free public UberEats data.
/ubereats/store/{store_id}/reviewsReturns the reviews snapshot embedded in an UberEats store page: aggregate rating, review count, and a sample of recent reviews (reviewer name, text, and relative/absolute date). This is a single on-page snapshot, not a full paginated feed. A store with no written reviews returns an empty reviews list. Credential-free public UberEats data.
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape UberEats
UberEats surfaces restaurant listings, menus, and reviews behind a rendered delivery app. Crawlora's UberEats endpoints return search results, store detail with full menu, and reviews as normalized JSON — no login or location-cookie juggling.
A delivery latitude/longitude with an optional keyword, or a specific store id from a search result.
Pass coordinates and a keyword to /ubereats/search, or a store id to /ubereats/store.
Receive restaurant name, rating, cuisine tags, delivery estimate, and — for a store — the full menu with item prices and a reviews snapshot.
Feed delivery-market dashboards and AI pipelines, or re-run to track menu and price changes over time.
FAQ
Send a delivery latitude/longitude (with an optional keyword) or a store id to Crawlora's UberEats endpoints and get restaurant search results, full store menus, and reviews as structured JSON — no login. Collect public data and respect UberEats' terms.
Yes. /ubereats/store returns current menu item prices per store — re-run it on a schedule to track price changes over time as JSON.
Collecting publicly accessible restaurant, menu, and review data is generally permissible if you respect UberEats' terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.