/zomato/restaurants/search

POST /api/zomato/restaurants/search

Price: 5 credits

Search Zomato restaurants in a city by mode (dining out / delivery / nightlife) with optional filters: keyword, cuisines, sort, minimum rating, maximum cost for two and amenities. Returns restaurant cards with name, rating, cuisines, cost for two, locality, distance and offers.

How to use it

Search Zomato restaurants in a city (by city slug e.g. 'bangalore'). Choose mode (dining_out, delivery, nightlife). Optional filters: keyword, cuisines (e.g. north_indian, chinese), sort (popularity/rating_high_to_low/cost_low_to_high/cost_high_to_low/distance), rating_min, cost_for_two_max, amenities (e.g. serves_alcohol, outdoor_seating, pure_veg). Each result has id, url, name, rating, rating_dining/rating_delivery, cuisines, cost_for_two, locality, distance and offers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• city string required — City slug (as used in Zomato URLs) (examples: "bangalore", "mumbai"; minLength: 1)
• mode string — Search vertical (default: "dining_out"; one of: "dining_out", "delivery", "nightlife")
• keyword string nullable — Free-text query (restaurant, cuisine or dish)
• cuisines array nullable — Filter by one or more cuisines (one of: "afghani", "american", "andhra", "arabian", "asian", "assamese", "awadhi", "bbq", "bakery", "bar_food", "bengali", "beverages", "biryani", "bohri", "bubble_tea", "burger", "burmese", "cafe", "cake", "cantonese", "chettinad", "chinese", "coffee", "continental", "desserts", "european", "fast_food", "finger_food", "french", "frozen_yogurt", "goan", "greek", "grilled_chicken", "gujarati", "healthy_food", "hyderabadi", "ice_cream", "indian", "indonesian", "israeli", "italian", "japanese", "juices", "kashmiri", "kebab", "kerala", "konkan", "korean", "lebanese", "lucknowi", "maharashtrian", "malaysian", "malwani", "mangalorean", "mediterranean", "mexican", "mithai", "modern_indian", "momos", "mughlai", "naga", "nepalese", "north_eastern", "north_indian", "oriental", "paan", "pancake", "parsi", "pasta", "persian", "pizza", "portuguese", "punjabi", "rajasthani", "rolls", "salad", "sandwich", "seafood", "shake", "sichuan", "sindhi", "south_indian", "spanish", "sri_lankan", "street_food", "sushi", "tea", "tex_mex", "thai", "tibetan", "turkish", "vietnamese", "wraps")
• sort string nullable — Sort order (one of: "popularity", "rating_high_to_low", "cost_low_to_high", "cost_high_to_low", "distance")
• rating_min number nullable — Minimum aggregate rating (e.g. 4.0) (min: 0; max: 5)
• cost_for_two_max integer nullable — Maximum cost for two (INR) threshold (min: 0)
• amenities array nullable — Filter by amenities / attributes (one of: "wheelchair_accessible", "credit_card", "buffet", "happy_hours", "serves_alcohol", "sunday_brunch", "desserts_and_bakes", "luxury_dining", "cafes", "hygiene_rated", "pubs_and_bars", "wifi", "pure_veg", "open_now", "fine_dining", "outdoor_seating", "online_bookings")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "ZomatoSearchCard")
• id integer required
• url string required
• name string required
• image string nullable
• rating number nullable
• vote_count integer nullable
• rating_dining number nullable
• rating_delivery number nullable
• cuisines array (default: [])
• cost_for_two number nullable
• cost_for_two_text string nullable
• currency string (default: "INR")
• locality string nullable
• address string nullable
• distance string nullable
• delivery_time string nullable
• is_promoted boolean (default: false)
• offers array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — City not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.