/zomato/restaurants

POST /api/zomato/restaurants

Price: 5 credits

Get full Zomato restaurant details by '{city}/{slug}' path or restaurant URL: name, cuisines, dining and delivery ratings, cost for two, address, geo coordinates, phones, opening hours, amenities, dining offers and photos.

How to use it

Fetch a single Zomato restaurant by '{city}/{slug}' path (e.g. 'bangalore/ishaara-residency-road-bangalore') or a full restaurant URL. Returns id, name, cuisines, rating (aggregate), vote_count, rating_dining/rating_delivery (+counts), cost_for_two, address, locality, city, latitude/longitude, phones, timing, opening_hours, status, highlights (amenities), offers, top_dishes, popular_for, known_for, static_map_url, photo_menus and images.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• restaurant string required — Restaurant as a '{city}/{slug}' path or a full restaurant URL (examples: "bangalore/ishaara-residency-road-bangalore", "https://www.zomato.com/bangalore/ishaara-residency-road-bangalore/info"; minLength: 1)

Response

• @type string (default: "ZomatoRestaurant")
• id integer required
• url string required
• name string required
• alias string nullable
• cuisines array (default: [])
• rating number nullable
• vote_count integer nullable
• rating_dining number nullable
• rating_dining_count integer nullable
• rating_delivery number nullable
• rating_delivery_count integer nullable
• image string nullable
• images array (default: [])
• thumbnail string nullable
• photo_menus array (default: [])
  • @type string (default: "ZomatoPhotoMenu")
  • label string required
  • pages_text string nullable
  • image string nullable
• top_dishes array (default: [])
• popular_for array (default: [])
• known_for string nullable
• static_map_url string nullable
• cost_for_two number nullable
• cost_for_two_text string nullable
• accepted_payments string nullable
• currency string (default: "INR")
• address string nullable
• locality string nullable
• city string nullable
• city_id integer nullable
• country string nullable
• country_id integer nullable
• zipcode string nullable
• latitude number nullable
• longitude number nullable
• phones array (default: [])
• timing string nullable
• opening_hours array (default: [])
  • @type string (default: "ZomatoOpeningHours")
  • days string required
  • timing string nullable
• status string nullable
• is_delivery_only boolean (default: false)
• is_permanently_closed boolean (default: false)
• is_temporarily_closed boolean (default: false)
• highlights array (default: [])
• offers array (default: [])
  • @type string (default: "ZomatoDiningOffer")
  • subtitle string nullable
  • offer_value number nullable
  • offer_type string nullable
• chain_url string nullable
• bookmark_count integer nullable
• share_url string nullable

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 — Restaurant not found (well-formed path but the restaurant does not exist) 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.