Uber Eats Restaurant Leads
Pricing
from $9.99 / 1,000 results
Uber Eats Restaurant Leads
Extract restaurant contact data from Uber Eats at scale — emails, phones, company IDs, VAT numbers, addresses. Territory, city, or URL mode. Lead gen, outreach, CRM enrichment. 31 countries. Export: CSV, JSON, Excel. Custom setup? corentin@outreacher.fr
Pricing
from $9.99 / 1,000 results
Rating
0.0
(0)
Developer

Corentin Robert
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Uber Eats Pro Scraper
Extract restaurant contact data from Uber Eats at scale — emails, phones, company IDs, VAT numbers, addresses — ready for outreach, CRM enrichment, and market intelligence.
Built for growth marketers, restaurant suppliers, food-tech entrepreneurs, and B2B sales teams.
Why use this?
Uber Eats lists thousands of restaurants with business details that are hard to collect manually. This Actor gives you:
- Direct contact data — Phone and email when available (EU legal disclosure)
- Business identifiers — Company ID (SIRET for France), VAT numbers for B2B verification
- Targeted lists — By country, region, city, or cuisine type
- Exhaustive coverage — Territory mode scans entire regions; City mode for specific markets
- Enrichment — Paste existing URLs to add missing fields to your CRM
Use cases: Pitch POS systems, delivery optimization, ingredients supply, franchise opportunities, market reports, competitor mapping.
Quick Start
- Open the Input tab
- Choose Territory mode
- Select Country (e.g. France) and Region (e.g. France – Île-de-France)
- Click Run
Results stream in the Dataset tab. Export as CSV, JSON, or Excel. No code needed.
Three Modes
Territory — Country or region
Best for market analysis and exhaustive lead lists. Scans all restaurants in a country or region. Filter by cuisine type.
{"mode": "territory","country": "fr","region": "fr:idf","categories": ["halal"],"maxResults": 2000}
| Region format | Example |
|---|---|
| Entire country | fr:all, be:all, us:all |
| Specific region | fr:idf (Île-de-France), fr:ara (Auvergne-Rhône-Alpes) |
City — One or more cities
Best for local campaigns and city-level outreach. Just type the city name — country is auto-detected (Annecy → France, Austin → US, Brussels → Belgium).
{"mode": "city","cityNames": ["Annecy", "Paris", "Lyon"],"maxResults": 500}
No need to select a country. Optional override: "fr:Annecy" forces France. Case and accents ignored.
URLs — Enrich existing links
Already have Uber Eats URLs? Paste them to extract or refresh contact data.
{"mode": "urls","startUrls": ["https://www.ubereats.com/fr/store/mcdonalds-paris/abc123"]}
Output — What you get
Each restaurant is one row:
| Category | Fields |
|---|---|
| Contact | email, phone, phoneFormatted, phoneLandline, phoneMobile |
| Business | companyId (SIRET for France), vatNumber |
| Location | address (street, city, region, postalCode, country, formatted), location (lat, lng) |
| Profile | name, url, foodCategories, priceRangeMin, priceRangeMax |
| Social proof | rating, reviewCount, imageCover |
Export: CSV (semicolon-separated for Excel), JSON, Excel.
Input Parameters
| Parameter | Description |
|---|---|
mode | territory / city / urls |
country | Country code. Territory mode. Ignored in City mode — auto-detected from city name |
region | countryCode:regionCode (e.g. fr:idf, be:all). Must match the selected country |
cityNames | City names — country auto-detected. Use fr:Annecy to force a country |
categories | Cuisine filters: halal, fast-food, sushi… Leave empty for all |
maxResults | Max restaurants to collect. Leave empty for unlimited |
collectEmails | Extract emails from restaurant pages. Activates residential proxy automatically |
startUrls | Restaurant URLs for URL mode |
Email Collection
Uber Eats includes restaurant email addresses in the legal disclosure section of each page. This data is only served when the request originates from an IP matching the restaurant's country — a legal transparency requirement in the EU.
When Collect emails is enabled, the scraper automatically routes requests through a residential proxy:
- European destinations (France, Belgium, Germany, Spain, Italy, UK, Netherlands, etc.) → France proxy
- North America (US, Canada) → United States proxy
- Other destinations → France proxy (best default for email coverage)
No proxy configuration required on your end.
Use Cases
| Goal | Mode | Config |
|---|---|---|
| Full France halal list | Territory | region: fr:all, categories: ["halal"] |
| Île-de-France restaurants | Territory | region: fr:idf |
| Paris + Lyon outreach | City | cityNames: ["Paris", "Lyon"] |
| Belgium delivery market | Territory | country: be, region: be:all |
| Enrich CRM from URLs | URLs | Paste URLs in startUrls |
| Multi-country comparison | Territory | Run per country, merge datasets |
Tips
Start small. Set maxResults: 100 on your first run. Check the output, then scale.
Use categories to narrow. halal, sushi, fast-food — fewer irrelevant leads, better conversion.
Territory for volume. City mode is faster per run; Territory gives exhaustive coverage when you need it.
Region must match country. If country is be, use be:all or a Belgian region — not fr:all.
FAQ
Why are some emails empty? Not all restaurants publish their email. When they do, it appears in the legal disclosure section of the page — only visible to IPs from the relevant country. Enable Collect emails to activate the residential proxy automatically.
What countries are supported? 31 markets: France, Belgium, Germany, Spain, Italy, United Kingdom, Netherlands, United States, Canada, Australia, Japan, and more. See the Country dropdown in the Input tab.
Can I run it on a schedule? Yes. Use Apify Scheduler to run weekly or monthly and keep your lead list fresh.
CSV separator?
Semicolon (;) for Excel compatibility.
Local Development
npm installnpm run buildapify run
Input: storage/key_value_stores/default/INPUT.json
Output: output.csv and storage/datasets/default/
Update reference (countries, regions, cities)
npm run update-referencenpm run build:schema
Deployment
$apify push
Support
Available for questions, custom requests, or integration help: corentin@outreacher.fr
Apache 2.0 — Last updated: March 2026