API Reference
Use Crawlora's Zomato API endpoints to extract supported public Zomato data as structured JSON. This documentation covers 5 active endpoints including Get one Zomato curated collection's restaurant list, List Zomato's curated restaurant collections for a city, Get one Zomato restaurant's detail, Get one Zomato restaurant's menu, and related APIs. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as url, city, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.
Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.
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"These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.
/zomato/collectionapiKey1 credit/requestReturns one Zomato curated collection's restaurant list (name, cuisines, locality, rating, and headline review count where Zomato's own response includes them). Reads the same underlying page-render source as /zomato/restaurant and /zomato/restaurant/menu, pointed at the collection's own page instead of a restaurant's.
Required params: url:query
/zomato/collectionsapiKey1 credit/requestReturns Zomato's own curated "best of" restaurant collections for a city (e.g. "Best pubs & bars", "Iconic restaurants", "Insta-worthy spots") -- distinct editorial groupings of restaurants, not a keyword/geo search. Each collection's url is the value /zomato/collection takes. Zomato curates collections for larger cities only; a real city it curates none for returns a 404.
Required params: city:query
/zomato/restaurantapiKey1 credit/requestReturns one Zomato restaurant's public detail by its canonical URL: name, address, locality, city, postcode, coordinates, phone, cuisines, headline rating plus Zomato's separate dining and delivery rating aggregates, the full weekly opening-hours table, open/closed and delivery-only/dark-kitchen status, and delivery metadata (ETA, minimum order, pickup availability). Zomato has no lighter restaurant-detail-only source -- this reads the same upstream as /zomato/restaurant/menu, just without the menu items.
Required params: url:query
/zomato/restaurant/menuapiKey1 credit/requestReturns one restaurant's menu grouped into categories, plus its restaurant summary. A category is named by Zomato's own sub-heading when it has one (e.g. "Veg Burgers") and otherwise by the menu section it sits under (e.g. "Burgers"), since most restaurants name only the section level. Each item carries a name, description, veg/non-veg flag, image, and price when Zomato's own anonymous response includes one -- confirmed live, item prices are commonly gated behind login for the delivery-ordering flow, so price is frequently absent even though the item itself is public.
Required params: url:query
/zomato/searchapiKey2 credits/requestReturns 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.
Required params: city:query
| Endpoint | API path | Method | Credits | Required params | Docs | Playground |
|---|---|---|---|---|---|---|
| Get one Zomato curated collection's restaurant list | /zomato/collection | GET | 1 credit/request | url:query | View docs | Try endpoint |
| List Zomato's curated restaurant collections for a city | /zomato/collections | GET | 1 credit/request | city:query | View docs | Try endpoint |
| Get one Zomato restaurant's detail | /zomato/restaurant | GET | 1 credit/request | url:query | View docs | Try endpoint |
| Get one Zomato restaurant's menu | /zomato/restaurant/menu | GET | 1 credit/request | url:query | View docs | Try endpoint |
| Search Zomato restaurants in a city | /zomato/search | GET | 2 credits/request | city:query | View docs | Try endpoint |