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
3
Documented params
18
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
12
Schema refs
5
{
"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
Every figure below is read from the live UberEats endpoint catalog — 5 endpoints, 18 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented UberEats endpoints, grouped into 3 request families — Store, Feed and Search.
18 request parameters are documented across those UberEats endpoints, 12 of them required — the full input contract is public before you write any integration code.
5 of the 5 UberEats endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
UberEats endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the UberEats endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/ubereats/store/{store_id}
/ubereats/feed
/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.
Sampled 14 Oct 2026: 20 items, 9 fields filled in every item, 2 not. rating: 4.2 to 5, median 4.7; storeUuid: “03ff567d-d8e4-5c66-8cc8-163217874b6a” and 19 other values.
MCP tool ubereats_search
/ubereats/feedReturns restaurants delivering to a specific location: name, rating, review count, delivery estimate, cuisine tags, and cover image.
Sampled 14 Oct 2026: 20 items, 9 fields filled in every item, 2 not. rating: 4.2 to 5, median 4.7; url: ubereats.com.
MCP tool ubereats_feed
/ubereats/store/{store_id}Returns an UberEats store: address, phone, rating, cuisine tags, hours tagline, and the full menu (sections with items, descriptions, and prices).
Sampled 14 Oct 2026: 12 items, 2 fields filled in every item. title: “Mains” and 10 other values; items: median 8 entries.
MCP tool ubereats_store
/ubereats/store/{store_id}/menuReturns the full menu for an UberEats store: section titles, items, item descriptions, prices, and availability status.
Sampled 14 Oct 2026: 13 items, 2 fields filled in every item. title: “Featured items” and 11 other values; items: median 9 entries.
MCP tool ubereats_store_menu
/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.
Sampled 14 Oct 2026: 37 items, 5 fields filled in every item. createdAt: 2021-10-26 to 2026-10-08.
MCP tool ubereats_store_reviews
Related APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
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.
Company coverage
Uber Technologies, Inc · UBER
UberEats is operated by Uber Technologies, Inc (UBER). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the UberEats endpoints above.
SEC filings & financials API →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 pull on 2026-10-27 from Midtown Manhattan returned 20 restaurants per page for both the feed and a pizza search, each with hasMore true.
/ubereats/store/{store_id} returns address, phone, rating, cuisine tags, hours tagline and the full menu with sections, items, descriptions and prices. /ubereats/store/{store_id}/menu returns just the menu with an availability status per item.
/ubereats/store/{store_id}/reviews returns the snapshot embedded in the store page: aggregate rating, review count and a sample of recent reviews with reviewer name and text. It is a sample, not a full archive.
feed and search both require latitude and longitude; 40.758, -73.9855 resolved to the new_york city. Results are tied to that delivery area, so store the coordinates with every row.
Both routes returned 20 restaurants with offset 0 and hasMore true. Continue with offset (or cursor on search) and stop when hasMore is false.
Each restaurant had a storeUuid, name, slug, URL, rating, delivery estimate text such as 12 min and image URL; the first feed row (Five Guys) showed a 4.6 rating from 8,000 reviews, while the first pizza search row had a rating but no review count. Use the store routes for menus and reviews.
Agent skills
Install a Crawlora agent skill and your agent can pull UberEats data as JSON through the documented API, without writing a scraper. These skills cover UberEats:
Compare restaurant menu breadth, matched dishes, bundles, and location-specific prices with the Crawlora API. Use for restaurant competitor…
npx skills add github.com/Crawlora-org/crawlora-skills --skill restaurant-menu-benchmarkingResearches restaurants and grocery/food delivery via the Crawlora API — Yelp reviews, OpenTable reservations, DoorDash and Uber Eats restaurant…
npx skills add github.com/Crawlora-org/crawlora-skills --skill restaurant-food-delivery-researchFAQ
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.
Not always. On 2026-10-27 the first feed row had a review count and the first pizza search row did not.