Deliveroo Scraper — Restaurants & Menu Prices

What does Deliveroo Scraper do?

Scrape Deliveroo restaurants (and optionally full menus with item prices) across major Deliveroo markets. Use neighborhood queries, location URLs, or direct restaurant menu URLs. Business restaurant / menu facts only.

Unofficial. This Actor is not affiliated with, endorsed by, or maintained by Deliveroo or Roofoods Ltd. It reads public restaurant listings and menus only.

Dashboards: connect Power BI, Tableau, Looker Studio, or Qlik to the dataset API — see Export to Power BI, Tableau, Looker Studio & Qlik near the end. AI agents: paste this Actor’s Store page URL into an Apify-capable agent (MCP / Claude / Cursor with Apify), create an Apify account and API token once, and the agent can run the Actor and wire up the output.

Compare with Just Eat: pair with Just Eat Restaurant Scraper + Just Eat Restaurant Menu Scraper for multi-platform UK/EU takeaway research.

Why use this Deliveroo scraper?

• 🛵 Listings by queries (city/neighborhood), location / locationUrl / address
• 📋 Optional scrapeMenu for item-level prices
• 🔗 Direct restaurantUrls always include full menu
• 🌍 domain market key (default co.uk)
• 🔑 Input names match the leading Store Actor for easy migration

What data can you extract from Deliveroo?

Restaurant identity, public URL, ratings, delivery metadata, and — when menus are enabled — menu items with prices and currency as exposed publicly.

Use cases

• UK / EU food-delivery market research
• Restaurant coverage by neighborhood
• Menu price monitoring for selected venues

How to scrape Deliveroo

1. Open this Actor in Apify Console.
2. Click Start on the prefilled london/soho query (maxResults 5, menus off).
3. Or paste restaurantUrls for a specific venue (always includes the full menu).
4. Set domain if not co.uk. Toggle scrapeMenu only when a location run needs items.
5. Export the dataset.

{
  "queries": ["london/soho"],
  "domain": "co.uk",
  "maxResults": 5,
  "scrapeMenu": false,
  "proxyConfiguration": { "useApifyProxy": true }
}

How much does it cost?

PPE: Actor start + each restaurant result. Around $4.49 / 1,000 on Free (see Pricing tab for tiers). Platform usage is included. Default run is 5 restaurants, menus off.

Input

Input	Notes
restaurantUrls	Direct menu URLs — always includes full menu (leave empty for location discovery)
queries	city/neighborhood e.g. london/soho
domain	Market TLD key, default co.uk
maxResults	Cap per query (prefill 5)
location / locationUrl / address	Alternate location inputs
scrapeMenu	Also fetch menus for location runs (off by default)
proxyConfiguration	Recommended for scale

Sample output

{
  "id": "12345",
  "name": "Example Kitchen",
  "uname": "example-kitchen-soho",
  "url": "https://deliveroo.co.uk/menu/London/soho/example-kitchen-soho",
  "rating": 4.6,
  "ratingCount": "(890)",
  "deliveryTimeMinutes": 25,
  "currencyCode": "GBP",
  "menuItemCount": 0,
  "address": {
    "address1": "1 Example Street",
    "city": "London",
    "neighborhood": "Soho",
    "postCode": "W1D 1AA"
  }
}

FAQ

Listings only or menus too?

Both. Location/query runs return restaurants; set scrapeMenu or pass restaurantUrls for menus.

Personal data?

Business restaurant / menu facts only. Optional public venue phone/email when shown on the page — never diner identities.

Just Eat vs Deliveroo in one city?

Run Just Eat Restaurant Scraper on an area URL, then this Actor on matching neighborhoods (queries). Add Just Eat Restaurant Menu Scraper when you need Just Eat item-level prices (Deliveroo: enable scrapeMenu here). Each Actor bills separately.

Legal?

Public restaurant and menu facts. This Actor is unofficial and not affiliated with Deliveroo.

Need help?

Open an issue on this Actor’s Issues tab in Apify Console.

Related Actors

Actor	Use together when…
Just Eat Restaurant Scraper	You compare restaurant coverage on Just Eat vs Deliveroo
Just Eat Restaurant Menu Scraper	You need Just Eat menu item prices to match Deliveroo menu rows
Deliveroo Scraper	(this Actor) — listings + optional menus

Profile: bakos_bence on Apify

For AI agents & LLM apps

Paste this Actor’s Apify Store URL into an agent that can use Apify (MCP, Claude, Cursor, etc.). With an Apify account and API token, the agent can set input, run the Actor, and fetch the dataset.

Actor ID: bakos_bence/deliveroo

Minimal input:

{
  "queries": ["london/soho"],
  "domain": "co.uk",
  "maxResults": 5,
  "scrapeMenu": false
}

Export to Power BI, Tableau, Looker Studio & Qlik

After a run, rows live in an Apify dataset. You can download JSON/CSV/Excel from the Dataset tab, or point BI tools at a CSV URL that refreshes when you scrape again.

Prefer the token in the URL (token=) — most tools only need “open this link as CSV”, with no custom headers.

Build a refreshable CSV URL

1. In Apify Console, open Settings → Integrations and copy an API token.
2. Save this Actor as a Task (optional but best for dashboards), run or schedule it once so there is a successful run.
3. Use the latest successful task run URL (replace TASK_ID and YOUR_TOKEN):

https://api.apify.com/v2/actor-tasks/TASK_ID/runs/last/dataset/items?format=csv&clean=true&status=SUCCEEDED&token=YOUR_TOKEN

Or, from any finished run, open the Dataset tab, copy the dataset ID, and use:

https://api.apify.com/v2/datasets/DATASET_ID/items?format=csv&clean=true&token=YOUR_TOKEN

Anyone with that URL can read the data — treat it like a password. For recurring dashboards, prefer the actor-tasks/…/runs/last/… form so refresh always hits the newest successful scrape.

Power BI

1. Open Power BI Desktop → Home → Get data → Web.
2. Paste the CSV URL (including token=).
3. When asked how to sign in, choose Anonymous → Connect.
4. Confirm the preview is a table (CSV). Load or Transform data as needed.
5. Publish / schedule refresh in the Power BI service using the same URL (task runs/last keeps it current after each scrape).

401: token missing/wrong, or you did not pick Anonymous.

Tableau

1. Install Tableau’s REST API connector from Tableau Exchange (Desktop 2023.3+).
2. Connect → To a Server → REST API.
3. Paste the CSV URL (including token=). Set response format to CSV.
4. If the connector asks for auth and the token is already in the URL, leave credentials empty / anonymous; otherwise paste the same token as a Bearer access token.
5. Create an extract. Refresh the extract after scheduled Task runs (or point at runs/last so each refresh loads the latest success).

Plain Text file connect still works if you download CSV from the Dataset tab once — use REST when you want repeatable refresh.

Looker Studio

Looker Studio has no strong built-in “private CSV API” connector. Use Google Sheets as the bridge:

1. Create a Google Sheet. In A1 enter:

=IMPORTDATA("https://api.apify.com/v2/actor-tasks/TASK_ID/runs/last/dataset/items?format=csv&clean=true&status=SUCCEEDED&token=YOUR_TOKEN")

2. Wait until columns fill (Sheets refreshes IMPORTDATA periodically).
3. In Looker Studio → Create → Report → Google Sheets → select that spreadsheet / tab.
4. Build the report. After each Actor/Task run, refresh the Sheet (or wait for IMPORTDATA) then refresh the Looker data source.

One-off alternative: Dataset tab → download CSV → Looker Studio File upload.

Qlik

REST connector (refreshable):

1. In Qlik Cloud / Qlik Sense → Add data → REST (or create a REST connection in the Data load editor).
2. URL = the CSV URL including token=. Method GET.
3. Set the expected response type to CSV (or use format=json and JSON mode).
4. Test connection, pick the table, Add / Load.
5. Reload the app after scheduled scrapes; with runs/last, each reload pulls the latest successful dataset.

Files: Dataset tab → download CSV → Add data → upload the file (fine for a single snapshot).

SEO keywords

deliveroo scraper, scrape deliveroo, deliveroo restaurant scraper, deliveroo menu scraper, uk food delivery data, deliveroo api alternative, takeaway menu prices deliveroo