Zomato Scraper icon

Zomato Scraper

Scrape restaurants and reviews from zomato.com. Get names, cuisines, ratings and votes, cost for two, address and coordinates, phone, per-vertical…

Start using this actor on Apify ↗Need a custom scraper?Contact us ↗

Zomato Scraper at a glance

Zomato Scraper is a ready-to-run Apify actor from abotapi for collecting ecommerce data. Its documented output includes id, name, change type (incremental mode), cuisines and rating, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $1.80 per 1,000 results on the Apify Free plan and from $1.00 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on
Apify cloud: console, API, schedules and integrations
Data type
Ecommerce, Automation, Developer Tools
Pricing
$1.80 per 1,000 results (Free plan), from $1.00 on paid plans
Output
Documented below · JSON, CSV, Excel
Inputs
21 options

Scrape restaurants and reviews from zomato.com. Get names, cuisines, ratings and votes, cost for two, address and coordinates, phone, per-vertical ratings, delivery info, plus per-review rating, author, date, text, photos and tags. Search a city feed or paste URLs.

What Zomato Scraper can do

  • Two ways to find restaurants. Search one or more city slugs on the Delivery or Dining Out feed, with an optional keyword, or paste restaurant, feed, and keyword-search links directly.
  • Full restaurant profiles. Cuisines, cost for two, per-vertical (Dining and Delivery) ratings, address, coordinates, phone numbers, chain name, and open/closed status, all on by default.
  • Reviews included. Attach up to 2000 reviews per restaurant with rating, author, date, like count, tags, and full text, sorted the way you want.
  • Offers filter. Narrow the Dining Out feed and keyword search to restaurants currently running a dining offer.
  • Built for schedules. Incremental mode returns only new and changed restaurants on recurring runs, with a resume option for one interrupted run.
  • Automatic mid-run checkpointing. A run that gets migrated or restarted by the platform picks up where it stopped instead of re-collecting and re-charging restaurants already pushed.

Choose what to collect

These inputs let you configure Zomato Scraper - Restaurants, Ratings & Reviews. Open the actor on Apify to enter your values and review the current options.

Supported input fields
InputWhat it controls
modestring · requiredsearch = pick a city and feed and walk it. url = paste restaurant, city-feed, or search URLs and walk them.

Choices: search, url

citiesarrayOne or more cities, typed as a name (Delhi NCR, Mumbai, Dubai) or as a Zomato city slug (ncr, mumbai, bangalore, dubai, london). Names are resolved with the site's own location lookup; a name that matches nothing stops the run with an error.
contextstringWhich feed to walk in each city.

Choices: delivery, dine-out

querystringOptional cuisine, dish, or restaurant keyword to narrow the city feed, e.g. pizza, biryani, cafe.
offersOnlybooleanApply Zomato's own Offers filter to narrow the feed to restaurants currently running a dining offer. Only affects the Dining Out feed and keyword search (Delivery has no such filter on Zomato).
urlsarrayPaste zomato.com links: city feeds (//delivery, /dine-out, /restaurants, /restaurants/ or /restaurants?q=), a delivery dish list (//delivery/dish-), a locality delivery list (//delivery-in-), a bare city page (/), the dine-out offers filter (?dining_payment_enabled_flag=true), or any restaurant page (/order, /reviews, /info, /menu, /photos). zomato.com, www and m hosts all work. Locality landing pages that list the whole city and unknown paths are skipped with a warning. Left untouched, the field scrapes one example of each shape. Alias: restaurantUrls.
fetchDetailsbooleanEnrich each restaurant with address, coordinates, phone, per-vertical ratings, and taxonomy from its page.
Show 14 more inputs
More input fields
InputWhat it controls
fetchReviewsbooleanAttach reviews (rating, author, date, text, photos, tags) to each restaurant.
maxReviewsintegerCap on reviews captured per restaurant. 0 disables reviews.
reviewsSortstringOrder of reviews within each restaurant.

Choices: popular, newest, oldest, rating-high, rating-low

maxItemsintegerTotal restaurants to return across all cities or URLs. 0 = no limit up to the cap of 100000.
maxPagesintegerSafety bound on feed pages walked per city or URL. Leave empty or 0 to walk all pages (the run still stops at Max restaurants, or the feed's own end).
resumeFromRunIdstringOptional. ID of a previous run of this actor (or a dataset ID). Restaurants already in that dataset are skipped, so this run returns only NEW restaurants (a delta). Combine both runs' datasets for the full set. For recurring daily monitoring of the same search, use Incremental mode below instead.
incrementalModebooleanTurn this on for daily or recurring monitoring. The first run returns all matching restaurants as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED restaurants. Turn on "Emit unchanged" or "Emit expired" only when you also want those restaurants returned (and billed). State is kept separately for each city/feed/URL and detail/review setup; use State key when you want to name or deliberately share a monitoring campaign. Changes are detected on the restaurant fields (name, cuisines, address, rating, cost, timings text, phones, reviews text). These live or rotating fields are ignored when comparing, but stay in the output: thumbnail, isOpenNow, deliveryTime, promoOffer, the relative review timestamp ("15 hours ago"), vote and review counters, and per-review like, comment and author counters and the per-review reply thread (comments) (add more under Ignore fields below). To continue one specific interrupted run instead, use Resume from a previous run above.
stateKeystringOptional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the city/feed/URL and detail/review settings, different searches then never mix state with each other.
emitUnchangedbooleanOff by default. Turn on to also return restaurants that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want the full snapshot every run.
emitExpiredbooleanOff by default. Turn on to also return restaurants that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search, not when Max restaurants capped it or when Resume was used. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking.
ignoreFieldsForChangesarrayOptional. Field names that must not make a restaurant count as UPDATED, in addition to the built-in list (thumbnail, isOpenNow, deliveryTime, promoOffer, the relative review timestamp, vote and review counters, per-review like, comment and author counters, and the per-review reply thread (comments)). A name matches at any depth, for example "costForTwoText" or "phones". Ignored fields still appear in the output; they are just not compared. Only used with Incremental mode.
mcpConnectorsarrayOptionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify then Settings then API & Integrations, then select it here. Notion gets a page-per-item export; other connectors get a best-effort write. Leave empty to skip. Supported: Notion, Linear, Airtable, Apify.
notionParentPageUrlstringURL or id of the Notion page under which item pages are created. Required only for the Notion export.
maxNotifyListingsintegerCap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

idID (text)
nameName (text)
changeTypeChange type (incremental mode) (text)
cuisineStringCuisines (text)
ratingRating (object)
costForTwoTextCost for two (text)
localityLocality (object)
cityCity (text)
deliveryTimeDelivery (text)
reviewsCountReviews (number)
urlURL (link)
changedFieldsChanged fields (incremental mode) (array)
Show 26 more fields
firstSeenAtFirst seen (incremental mode) (date)
lastSeenAtLast seen (incremental mode) (date)
addressAddress (text)
countryCountry (text)
zipcodeZip code (text)
latitudeLatitude (number)
longitudeLongitude (number)
phonesPhones (array)
chainNameChain (text)
establishmentsEstablishment types (array)
ratingsByVerticalRatings by vertical (object)
timingOpening hours (object)
detailScrapedDetails fetched (boolean)
ratingTextRating text (text)
textReview (text)
authorAuthor (text)
authorProfileUrlAuthor profile (link)
authorReviewsCountAuthor reviews (number)
authorFollowersCountAuthor followers (number)
timestampDate (text)
likeCountLikes (number)
commentCountComments (number)
experienceExperience (text)
tagsTags (array)
photosPhotos (array)
reviewUrlReview URL (link)

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "id": "18685577",
  "name": "Olive Bar & Kitchen",
  "url": "https://www.zomato.com/ncr/olive-bar-kitchen-mehrauli-new-delhi",
  "cuisines": [
    "Italian",
    "Mediterranean",
    "Continental"
  ],
  "cuisineString": "Italian, Mediterranean, Continental",
  "locality": "Mehrauli, New Delhi",
  "costForTwoText": "₹4,000 for two",
  "rating": {
    "aggregate": 4.6,
    "text": "4.6",
    "subtitle": "Very Good",
    "votes": 3049,
    "color": "3F7E00"
  },
  "ratingsByVertical": {
    "DINING": {
      "rating": 4.6,
      "reviewCount": 3049,
      "subtitle": "Very Good"
    },
    "DELIVERY": {
      "rating": 4.1,
      "reviewCount": 1200,
      "subtitle": "Very Good"
    }
  },
  "address": "One Style Mile, Kalka Das Marg, Mehrauli, New Delhi",
  "city": "New Delhi",
  "country": "India",
  "latitude": 28.5245,
  "longitude": 77.1855,
  "phones": [
    "+911234567890"
  ],
  "chainName": "Olive Group",
  "hasPromo": true,
  "promoOffer": "20% OFF",
  "detailScraped": true,
  "reviews": [
    {
      "id": "r123",
      "rating": 5,
      "ratingText": "Excellent",
      "author": "Jane D.",
      "timestamp": "5 days ago",
      "text": "Fantastic ambience and food.",
      "likeCount": 3,
      "commentCount": 0,
      "tags": [
        "Great Ambience"
      ]
    }
  ],
  "reviewsCount": 1,
  "source": "search"
}

Ways to use this data

  • Food delivery market research: compare cuisines, cost for two, and delivery times across a city or neighborhood.
  • Reputation and review analysis: pull full review text and ratings to track sentiment for specific restaurants or chains.
  • Restaurant discovery apps: feed structured listings into your own search, map, or recommendation tool.
  • Competitive monitoring: schedule the actor and use incremental mode to catch new listings, rating changes, or closures over time.
  • Local business directories: collect address, phone, and status data for restaurants in a city or region.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Zomato Scraper return?

The documented output for Zomato Scraper includes id, name, change type (incremental mode), cuisines, rating, cost for two, locality and city. Availability of each field depends on the source page and the selected mode.

How much does Zomato Scraper cost?

It costs $1.80 per 1,000 results on the Apify Free plan and from $1.00 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I get only new or changed restaurants on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated restaurants, and unchanged ones are not billed. Turn on Emit expired if you also want restaurants that disappeared marked EXPIRED; that only fires once a run has scanned the entire tracked search without a cap or a resume.

Why did my run return fewer restaurants than expected, or none at all?

Most causes return an empty or partial dataset rather than failing the run: a city slug or keyword with no results, a feed page that couldn't be read after retries, or Max restaurants capping the run early. Check the run's status message for the reason. The run fails outright only in two cases: an invalid resumeFromRunId (a run or dataset ID that doesn't resolve), or combining resumeFromRunId with incremental mode on a search that already has saved incremental state.

Can I use it with AI agents or MCP?

Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear, or Airtable.

Ready to collect with Zomato Scraper?

Run it on Apify with your own input and export the results as JSON, CSV or Excel.