Uber Eats Restaurants & Menus Scraper
Pricing
from $2.49 / 1,000 results
Uber Eats Restaurants & Menus Scraper
Uber Eats Scraper SD - Uber Eats Scraper is a restaurant data tool that extracts public Uber Eats stores and full menus from store links or city pages: name, address, phone, cuisines, rating, reviews, opening hours, menu sections, items and prices.
Pricing
from $2.49 / 1,000 results
Rating
0.0
(0)
Developer
Neuro Scraper
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
15 days ago
Last modified
Categories
Share
Uber Eats Scraper - restaurants and full menus from Uber Eats
The Uber Eats Scraper extracts public Uber Eats stores with their complete menus: store name, cuisines, price range, rating and review count, phone, full address with coordinates, opening hours, images, and every menu section with item names, descriptions and prices. Give city slugs or paste store, city, category or neighborhood links. No Uber Eats account, login or delivery address is used.
Input
| Field | Type | Default | Meaning |
|---|---|---|---|
cities | list | austin-tx (prefill) | City part of an Uber Eats city URL: austin-tx, gb/london-eng, fr/paris-idf; "Austin, TX" also works for US cities |
startUrls | list | empty | Store URLs and/or city, category (/category/austin-tx/pizza) or neighborhood pages |
maxItems | integer | 20 | Total stores to return |
includeMenu | boolean | true | Put the full menu in each row |
maxMenuItems | integer | 0 | Cap menu items per store (0 = all) |
proxyConfiguration | proxy | Apify RESIDENTIAL | Proxy used for Uber Eats |
Output (one row per store)
| Field | Meaning |
|---|---|
storeId, name, url | Uber Eats store id, name, link |
cuisines, priceRange, rating, reviewCount | Cuisine tags, $ to $$$$, average rating, number of ratings |
phone, street, city, region, postalCode, country, latitude, longitude | Contact and location |
openingHours | List of {days, opens, closes} |
imageUrl, images | Store images |
menuSectionCount, menuItemCount, currency, minItemPrice, maxItemPrice | Menu summary |
menu | Sections with items {name, description, price} (omitted when includeMenu is off) |
source, scrapedAt | Input that produced the row, time |
Measured limits (2026-10-03, local runs)
- About 2 s per store (one 1-2 MB page each) plus one request per list page of 20-26 stores: 20 stores in 39 s, 45 in 97 s.
- City pages kept giving new stores up to page 20 (the deepest page tested).
- Grocery, convenience and wholesale stores (Costco, Co-op, Sainsbury's) publish no menu in their page:
their rows have store data and
menuItemCount0. - Delivery fees, ETAs and live open/closed state depend on a delivery address and are not included.
- Tested without proxy from one residential IP; no bot challenge was met. A challenge is never solved: the Actor retries on a new IP, then skips the target with an error in the log.
Example
{"cities": ["austin-tx", "gb/london-eng"], "maxItems": 100, "maxMenuItems": 50}