Zomato API endpoint
Use Crawlora's Zomato Search API to extract supported public Zomato data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/zomato/searchReturns restaurants in a Zomato city, optionally filtered by a keyword. With no query this reads Zomato's own city-wide delivery listing, which pages through an opaque cursor (~12 restaurants per page: pass a response's next_cursor back as cursor until has_more is false, which marks the end of the city's listing) and accepts Zomato's own sort and Pure Veg filters; with a query it uses Zomato's own keyword search across restaurant names, dishes, and cuisines, which returns a single unpaginated result set. Each restaurant carries its url (the value the restaurant and menu endpoints take), name, cuisines, cost for two, rating, distance from the city location, delivery time, whether Zomato currently delivers from it, whether the placement is promoted (sponsored), and — on the plain city-wide listing — Zomato's own headline offer badges. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| city | string | Yes | Zomato public city slug, e.g. \ | ||
| query | string | No | Optional keyword to search restaurant names, dishes, or cuisines by. Omit for the plain city-wide delivery listing. | ||
| sort | string | No | Sort order for the city-wide listing (used only when query is omitted) Allowed values: popularity_desc, rating_desc, cost_asc, cost_desc | ||
| pure_veg | boolean | No | When true, restricts the city-wide listing to restaurants Zomato itself marks Pure Veg (used only when query is omitted) | ||
| cursor | string | No | Opaque pagination cursor from a previous city-wide listing response's next_cursor. Carries its own sort/pure_veg selection, so pass it on its own. | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/zomato/search?query=coffee&sort=popularity_desc&pure_veg=true" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"city": "mumbai",
"total_results": 1394,
"has_more": true,
"next_cursor": "eyJwYiI6Ins...",
"restaurants": [
{
"id": "34269",
"name": "Persian Darbar",
"url": "https://www.zomato.com/mumbai/persian-darbar-byculla",
"cuisines": [
"Biryani",
"Mughlai",
"North Indian"
],
"rating": 4.2,
"rating_count": "54.7K",
"cost_for_two": "₹2,100 for two",
"locality": "Byculla, Mumbai",
"address": "5, Alexandra Terrace, Byculla, Mumbai",
"image_url": "https://b.zmtcdn.com/data/pictures/9/34269/img.jpg",
"delivery_time": "38 min",
"distance": "1.2 km",
"is_promoted": true,
"offers": [
"50% OFF"
],
"is_serviceable": true
}
]
}
}Request schema
No body schema
Response schema
#/definitions/zomato.searchResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | Code is the HTTP status code or a custom code used to indicate the result of the request @example 200 | |||
| data | zomato.SearchResponse | No | ||||
| data.city | string | No | ||||
| data.has_more | boolean | No | ||||
| data.next_cursor | string | No | ||||
| data.query | string | No | ||||
| data.restaurants | array | No | ||||
| data.restaurants[].address | string | No | ||||
| data.restaurants[].cost_for_two | string | No | ||||
| data.restaurants[].cuisines | array | No | ||||
| data.restaurants[].delivery_time | string | No | DeliveryTime is Zomato's own delivery ETA (e.g. "38 min"), present on results that carry its delivery-order metadata. Both search sources carry it but in different display shapes -- the city-wide listing serves a bare "38 min", keyword search a prefixed "Delivery in 38 min" -- so it is normalized to the bare form (see normalizeDeliveryTime). Absent for a restaurant Zomato is not currently delivering from. | |||
| data.restaurants[].distance | string | No | Distance is Zomato's own display distance from the resolved city location to the restaurant (e.g. "1.2 km"). Present on both search paths. | |||
| data.restaurants[].id | string | No | ||||
| data.restaurants[].image_url | string | No | ||||
| data.restaurants[].is_promoted | boolean | No | IsPromoted reports whether Zomato itself labels this a promoted (sponsored) placement rather than an organic result. | |||
| data.restaurants[].is_serviceable | boolean | No | IsServiceable reports whether Zomato will currently deliver here from the resolved location. A pointer so a source that does not carry the flag omits it rather than reporting a false "not serviceable". | |||
| data.restaurants[].locality | string | No | ||||
| data.restaurants[].name | string | No | ||||
| data.restaurants[].offers | array | No | Offers carries Zomato's own headline offer badges for this restaurant (e.g. "50% OFF", "₹100 OFF"). Only the city-wide listing carries them -- keyword search results do not. | |||
| data.restaurants[].rating | number | No | ||||
| data.restaurants[].rating_count | string | No | ||||
| data.restaurants[].url | string | No | ||||
| data.total_results | integer | No | ||||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/zomato/search?query=coffee&sort=popularity_desc&pure_veg=true" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms