Zomato restaurant reviews

GET https://api.api.sh/zomato/v1/reviews
1 credit / call e-commerce try it in the playground →

A restaurant's Zomato reviews by link: rating and rating label, review text, date, experience (dining or delivery), reviewer name, link, review count and followers, likes, comment count, photos, tags and link, with the restaurant's total review count. Sort by newest, oldest, highest or lowest rating. 5 reviews per page: pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
url string A zomato.com restaurant link, e.g. https://www.zomato.com/ncr/haldirams-connaught-place-new-delhi. Example: https://www.zomato.com/ncr/haldirams-connaught-place-new-delhi
sort newest | oldest | highest | lowest newest (default), oldest, highest or lowest rating first.
page integer Page number. Pass next_page from the previous response; next_page is null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/zomato/v1/reviews?url=https%3A%2F%2Fwww.zomato.com%2Fncr%2Fhaldirams-connaught-place-new-delhi" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.