Paste a Deliveroo search or restaurant-list URL and get every restaurant on it back as rows: the name, its cuisines, the rating and review count, the price range, a split address, the phone number, and links to the page and the image. Point it at a single restaurant instead and you get that one row.
Build the search on Deliveroo the way you normally would - a city, a cuisine, a postcode - then hand us the address from the bar.
One row per restaurant, tagged with the query it came from. Deliveroo sits behind Cloudflare, so live runs need a residential proxy.
A restaurant-list or search URL fans out to all the restaurants listed on it, not just the first. That is the difference between reading a market and reading a page - and it is the same run either way.
Street, city, postcode and country come as four columns rather than one line to parse. That is what makes a postcode-level view of who delivers where a sort rather than a regex.
The two things you would otherwise eyeball across a hundred cards - what a restaurant cooks and roughly what it costs - arrive as columns you can group by.
What a Deliveroo listing carries about a restaurant: who it is, what it cooks, how it scores, where it is and how to reach it.
Two things we would rather state than let you assume. The first: the table below names the thirteen columns and says what each field is for - and it stops there. It does not tell you what scale rating uses, what vocabulary price_range uses, or whether cuisines holds one value or several. Those are answers a populated export gives, and every run export we hold came back with a header row and no data rows.
One structural point is worth making, because it is verifiable and it matters: this export carries no companion scale column for rating. Our reviews export does - it ships max_rating next to the score - but this one does not, which means the scale cannot be recovered from the file itself. That is a reason to check it against a real run rather than to assume, and it is why this page prints no number.
The second: Deliveroo sits behind Cloudflare. Live results need a residential proxy, and that is why the exports we hold are empty rather than because the column set is uncertain - the column set is corroborated twice over. Run a small free-tier job against a search you care about; the header row and first few rows of that file are the definitive answer.
The export's header row, in order. Descriptions say what each field is for; they deliberately claim nothing about its format, scale or vocabulary - see the note above.
max_rating - so confirm the scale against a real run before you compare these against another platform.The names are solid; the contents are not yet. The thirteen columns above and their order are corroborated by two independent sources - the XLSX header row of four separate run exports and the published column array - so build your schema around those names with confidence. What this page will not tell you is what the cells hold: every export we hold is a header with no rows beneath it. Note the one structural gap: there is no max_rating here the way there is in the reviews export, so the rating's scale is not recoverable from the file and needs confirming against a real run. And Deliveroo sits behind Cloudflare, so a live run needs a residential proxy - that is the reason those exports are empty, not any doubt about the column set.
Point it at a restaurant-list or search page to take every restaurant on it, or at one restaurant when you already know which. Both come back in the same thirteen columns, one row per restaurant.
A few examples of what a delivery listing is worth once it is a table rather than an infinite scroll.
Take the restaurant-list URL for an area and every restaurant on it comes back as a row, with the address already split. Counting the competition in a delivery radius stops being a scrolling exercise and becomes a group-by.
Group the rows by cuisine and price band and you can see which combination an area is short of. That is a question about the whole listing, which is exactly the thing a page of cards will not answer.
Name, split address and phone number arrive as their own columns, so a search becomes a call list. If you sell to restaurants - packaging, POS, ingredients - this is the shape you actually want.
No subscription, no minimum, no recurring bill. Your first 500 rows are on us - after that, pay-as-you-go at the same flat rate as every other scraper here.
Every new account, one-time. No credit card required. Per-query limits, file upload and every export format included.
Roughly $2 per 1,000 restaurants. The pre-flight estimator shows the row count and credit cost before a run starts - no surprise bills, no compute units to translate.
Volume pricing, dedicated workers and an SLA for mapping many areas on a schedule. Tell us your numbers and we will quote.
LIVESCRAPER10 at checkout.This one gives you the list. These three tell you how each name on it is doing.
The obvious next step: this run gives you the restaurant URLs, and that one turns each of them into its reviews. One row per review instead of one per restaurant.
The Dutch delivery platform, for the markets Deliveroo does not cover. Useful when you are mapping delivery across more than one country.
Every restaurant in an area, not just the ones on Deliveroo. The gap between the two lists is the set of places that do not deliver - which is often the interesting question.
Short answer: these listings are public business information - which makes this one of the more straightforward pages on the site.
Everything collected here is shown on a public Deliveroo page to any visitor, signed in or not: the restaurant name, its cuisines, the rating and review figure, the price band, the address, the phone number and the image. No login, no paywall, nothing behind an account.
This export is about businesses, not people. There are no reviewer names, no review text, no customer details and no columns for any of them - the restaurant's phone number and address are the contact details it publishes precisely so customers can use them. That makes this materially lighter on data-protection obligations than our reviews export, which does carry reviewer names. If you load these rows into a CRM for outreach, ordinary marketing rules still apply, but you are not handling review authors' personal data here.
One practical note that is technical rather than legal: Deliveroo sits behind Cloudflare, so live results need a residential proxy. And as always, Deliveroo's own terms govern automated collection from their site - read them before you scale rather than relying on the fact that the pages are public. We run no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
Your first 500 rows are free - no card, no subscription. After that it is $0.002 per row, flat.
A Deliveroo listing page is a market in a scroll: every restaurant that delivers to an area, with its cuisines, its rating, its price band and its address, shown a card at a time. The Deliveroo Scraper turns that page into rows. You submit a restaurant-list or search URL and every restaurant on it comes back as a record - or point it at a single restaurant and get that one row. Thirteen columns either way, one row per restaurant, with the address already split into street, city, postcode and country.
The two input modes are the thing worth understanding before your first run, because they decide what a run costs. A search URL fans out to the whole listing; a single restaurant URL returns one row. You can mix both in the same job, and because billing is per row, mapping one postcode is cheap enough to do before you commit to mapping a city. The url column that comes back is itself valid input, so a search run hands you the addresses you need to go deeper on individual restaurants later.
Two honest notes before you start. Deliveroo sits behind Cloudflare, so live results need a residential proxy; that is stated up front rather than left to be discovered. And this page's data dictionary names the thirteen columns and says what each is for, but claims nothing about their formats or vocabularies, because every run export we hold came back as a header row with no data rows. One structural point is verifiable and stated: there is no companion scale column for rating in this export, unlike our Deliveroo reviews export which ships max_rating - so the scale cannot be recovered from the file and should be confirmed against a real run.
Take a small free-tier run against a search you care about and the header row and first few rows are the definitive answer for the area you are actually mapping. Your first 500 rows cost nothing and need no credit card, and after that it is $0.002 per row, flat.