Zomato Reviews Scraper avatar

Zomato Reviews Scraper

Under maintenance

Pricing

from $4.99 / 1,000 results

Go to Apify Store
Zomato Reviews Scraper

Zomato Reviews Scraper

Under maintenance

An advanced, high-speed e-commerce scraper designed for real-time price monitoring and competitor intelligence. Extracts product titles, current pricing, discounts, stock availability, specifications, images, and seller ratings from Zomato. Perfect for inventory tracking, drop-shipping research, ...

Pricing

from $4.99 / 1,000 results

Rating

0.0

(0)

Developer

Coding Frontned

Coding Frontned

Maintained by Community

Actor stats

0

Bookmarked

26

Total users

1

Monthly active users

15 days ago

Last modified

Share

Collect public restaurant reviews from Zomato restaurant pages. The Puppeteer actor opens each supplied restaurant URL, discovers the restaurant ID, calls Zomato's review endpoint in the browser context, transforms review entities, and emits one dataset row per complete review.

The actor can use supplied session cookies but does not promise access to private reviews or bypass authentication and anti-bot controls.

Input

restaurantUrls is required and accepts 1–20 HTTPS Zomato restaurant URLs. maxReviewsPerRestaurant defaults to 20 and is bounded at 100. headless controls browser visibility, cookies optionally supplies validated Zomato-domain cookie objects, and proxyConfiguration can explicitly enable an Apify proxy. Direct access is the default; enabling a proxy without a group uses the standard pool rather than silently selecting residential traffic.

Example input

{
"restaurantUrls": [
"https://www.zomato.com/mumbai/the-big-fish-co-dadar-west/info"
],
"maxReviewsPerRestaurant": 20,
"headless": true,
"proxyConfiguration": {
"useApifyProxy": false
}
}

Output

Each row has recordType zomato_review, review and reviewer identity, review text/date, rating details, positive and negative tags, likes, comments, management responses, photos, external links, restaurantUrl, resId, source, and scrapedAt.

Production runs do not capture page images. For explicit troubleshooting only, set the Actor environment variable ZOMATO_DEBUG_SCREENSHOTS=true; named PNG diagnostics are then written to the default key-value store. Screenshots can contain page/session state and should be handled as sensitive debugging artifacts.

Example output

{
"recordType": "zomato_review",
"review_id": "review-123",
"review_text": "Great food and attentive service.",
"review_text_short": "Great food and attentive service.",
"date": "2026-08-10",
"rating_value": 4.5,
"user_id": 1234,
"user_name": "Example reviewer",
"like_count": 3,
"comment_count": 0,
"restaurantUrl": "https://www.zomato.com/mumbai/example/info",
"resId": "12345",
"source": "zomato",
"scrapedAt": "2026-08-16T00:00:00.000Z"
}

Cost and limitations

Puppeteer browser time, review pages, cookies, retries, and proxy traffic determine cost. Zomato can change API responses, require login, block automation, or omit reviews. Only complete rows with review ID, reviewer, rating, text, and date are pushed; a run with no complete rows fails.

Use only public or lawfully supplied session data and handle reviewer information responsibly.