Zomato Menus and Restaurant Ratings as Data
Zomato restaurant pages bundle the three things most restaurant-intelligence projects actually need: star ratings with review counts, full menus with item prices, and cuisine tags.
This page explains how a single HTTP request against a Zomato URL returns that bundle, which request parameters you reach for when a page misbehaves, and how to tell a blocked request apart from a page that simply needs JavaScript or a different country route.
What a Zomato request returns
A Zomato restaurant page carries restaurant name, cuisine, menu items, item prices, ratings, review count, delivery time and location. The API renders the page in a real browser, rotates the outbound IP, and hands back the response your scraper can act on — HTML or JSON depending on what you ask for. There is no proxy fleet, headless Chrome install or bot-bypass layer to maintain on your side. Menus are location-sensitive: the same restaurant can show different items and prices depending on the delivery zip code the page resolves to, which is why geo routing matters more here than on a static content site.
Three data patterns that cover most projects
Most Zomato scraping work falls into one of three shapes. Pick the shape first, then the parameters.
- Rating tracking. Capture star score and total review count per outlet to follow restaurant quality over time or benchmark competitors. Feeds restaurant-quality and competitor-research workflows.
- Menu collection. Capture menu items, item prices, dish descriptions and category sections per restaurant. Feeds menu-pricing intelligence workflows.
- Cuisine classification. Capture cuisine type tags, dietary-preference flags and category metadata per restaurant. Feeds culinary-market research workflows.
A single restaurant URL can serve all three at once; the difference is which fields you keep and how often you re-request the page.
Which request parameter solves which problem
The base request is a URL plus your API key. When a page needs more, four advanced parameters cover the common failure modes. Use this map to choose the smallest change that fixes the symptom.
- `render_js` — the page's content is injected by client-side JavaScript and the raw HTML is thin. Set
render_js=true; the page runs in a real headless browser server-side and you get the post-render HTML back. - `stealth_proxy` — the target is aggressive and normal rotation is not enough. Enable it on the request to push harder against bot detection.
- `country_code` — content varies by geography (menus, availability, pricing). Pass a country code to route through a residential IP in that country.
- `ai_extract_rules` — you want structured JSON without writing selectors. Send a natural-language spec and get structured output back.
Screenshots, JavaScript scenarios (click, scroll, wait, custom JS) and Markdown output are separate capabilities you can layer on when the data you need is visual or LLM-bound rather than field-bound.
Worked example: one restaurant, four parameters
Suppose you want a single Zomato restaurant page as structured data, and you have already seen that the raw HTML comes back nearly empty. A workable sequence:
- Send the restaurant URL with your API key as the base request. Confirm you get a response at all — a hard block looks different from a thin page.
- Add
render_js=true. The menu and rating blocks that were missing from the raw HTML should now be present in the returned HTML. - If the returned menu items do not match the city you expect, add
country_codefor that country and re-request. Content that varies by geo is the usual cause of a menu that looks wrong rather than missing. - If you still see challenge pages rather than restaurant content, enable
stealth_proxyon the request. - Once the HTML is correct, either parse it yourself or send an
ai_extract_rulesspec describing the fields you want (for example restaurant name, rating, review count, menu item names and prices) and take the structured JSON back.
Each step changes one variable, so you can tell which parameter actually fixed the problem and keep the request as cheap as possible.
Blocked, unrendered or geo-mismatched?
These three failures look similar in a log but need different fixes:
- Blocked. You get a challenge page, an error status, or content that is clearly not the restaurant. Fix:
stealth_proxy. - Unrendered. You get the page shell but the menu, ratings or prices are absent. Fix:
render_js=true. - Geo-mismatched. You get a complete page, but the menu, availability or pricing does not match the market you are targeting. Fix:
country_codefor the intended country.
If none of those apply and the page is simply slow or throttled, the issue is request pacing rather than a parameter — see the concurrency note below.
Concurrency, not per-target rate limits
The API applies concurrency limits per plan rather than per-target rate limits. If Zomato throttles aggressive patterns, space out requests or use multiple sessions. Plan-level concurrency is the ceiling on simultaneous requests; the per-plan numbers are listed in the plan matrix below.
Getting to a first request
Create an account to get an API key and starting credits. Client libraries exist for Python, Node.js, Go, PHP, Ruby and Java, plus raw cURL examples, so the first request is a function call or a single HTTP call rather than a browser stack. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in any of those languages — useful if you want to confirm a request shape before writing code around it.
Plans and credit costs
Plans differ by monthly API credits, concurrent requests and support level. The credit cost of a request depends on which features you enable: base requests start at 1 credit each, JS rendering adds cost per successful request, and premium proxies cost more again depending on whether JS rendering is also on. Credits are valid for one month and do not roll over. The plan matrix below lists every tier and its included features, and the credit-cost table below states the per-request rules; treat both as a dated reference and confirm current terms before committing to a tier.
Data handling and compliance posture
The service states it does not collect or store personal data from scraped sites unless the user explicitly requests it, and positions itself as GDPR and CCPA aligned. That is a statement about the vendor's handling, not a substitute for your own lawful-basis analysis when you scrape restaurant or review data that may include personal information. Check the acceptable-use policy and the target site's terms before running at scale.
| Plan | Price /mo | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Prices are exclusive of VAT. Figures are a dated reference and should be re-checked against the current pricing page before purchase.
| Feature | Credit cost |
|---|---|
| Base request | 1 credit each |
| JS rendering enabled | 5 credits per successful request |
| Premium proxies, JS rendering disabled | 10 credits per successful request |
| Premium proxies, JS rendering enabled | 25 credits per successful request |
Credits are valid for one month and do not roll over. Costs are per successful request and are a dated reference; confirm current terms before budgeting.
Frequently asked questions
How do I start scraping Zomato?
Create an account, take the API key, and send a GET request with the target Zomato URL. The service renders the page, rotates proxies, and returns the data. Starting credits are available to test the request before committing to a plan.
Will I get blocked when scraping Zomato?
Requests go through rotating residential proxies and a real headless browser, so they resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request.
Can I scrape Zomato without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL. You can also run the request from an n8n workflow if you prefer a visual automation tool.
How do I handle JavaScript when scraping Zomato?
Pass render_js=true on the request. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.
Can I scrape Zomato from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when menus, availability or pricing vary by geography.
What's the rate limit for scraping Zomato?
The API applies concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.
Which Zomato fields can I get back in one call?
Restaurant name, cuisine, menu items, item prices, ratings, review count, delivery time and location all come back from a single restaurant page request. If you want structured JSON rather than HTML, add an ai_extract_rules spec describing the fields you want.
How do I tell a blocked request from a page that needs rendering?
A blocked request returns a challenge page, an error status, or content that is clearly not the restaurant — fix with stealth_proxy. An unrendered page returns the shell but no menu, ratings or prices — fix with render_js=true. A complete page whose menu does not match your target market is a geo mismatch — fix with country_code.