# Get reviews

Fetch paginated public Zomato reviews with reviewer metadata, ratings, likes/comments, photos, owner responses, and continuation metadata.

- Platform: [Zomato](https://docs.upscrape.com/docs/platforms/zomato)
- Capability ID: `zomato.restaurant.reviews`
- Cost: 1 credit per request
- Maximum runtime: 30 seconds
- Execute endpoint: `POST https://data.upscrape.com/execute`

## Request

Use the exact public capability ID in the shared execute envelope.

```bash
curl --request POST \
  --url https://data.upscrape.com/execute \
  --header "Authorization: Bearer $UPSCRAPE_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Prefer: wait=30" \
  --data '{
  "input": {
    "filter": "dining",
    "limit": 5,
    "page": 1,
    "restaurant_id": "18439027",
    "sort": "newest"
  },
  "capability": "zomato.restaurant.reviews"
}'
```

## Input


| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `filter` | `string` | No | Allowed values: `dining`, `delivery`. Default: `dining`. |
| `limit` | `integer` | No | Maximum reviews to return. Results preserve Zomato's five-review page boundaries. From 5 to 100. Default: `20`. |
| `page` | `integer` | No | One-based result page to fetch. At least 1. Default: `1`. |
| `res_id` | `string` | No | Compatibility alias for restaurant_id. |
| `restaurant_id` | `string` | No | Canonical numeric Zomato restaurant identifier. |
| `sort` | `string` | No | Sort order for returned results. Allowed values: `newest`. Default: `newest`. |

### Example input

```json
{
  "filter": "dining",
  "limit": 5,
  "page": 1,
  "restaurant_id": "18439027",
  "sort": "newest"
}
```

## Response

Successful output is returned in `results[0].data`.

Raw platform output is intentionally open-ended and may evolve with the upstream source.

### Illustrative sample output

This example shows one response. Values and optional fields vary with the data available.

```json
{
  "count": 1,
  "fetched_at": "2026-09-24T08:48:44Z",
  "filter": "dining",
  "pagination": {
    "has_more": true,
    "next_page": 2,
    "page": 1,
    "total_pages": 523
  },
  "res_id": "18439027",
  "restaurant_id": "18439027",
  "reviews": [
    {
      "comments_count": 0,
      "experience": "dining_order",
      "fetched_at": "2026-09-24T08:48:44Z",
      "likes_count": 0,
      "rating": 5,
      "rating_text": "Excellent",
      "rating_type": "DINING",
      "restaurant_id": "18439027",
      "review_id": "515759332",
      "review_text": "Food and service were very good.",
      "timestamp": "16 hours ago",
      "user": {
        "name": "Reviewer"
      }
    }
  ],
  "sort": "newest"
}
```
### Illustrative output fields

Derived from the sample above for orientation only. These fields are not a fixed response schema.

| Path | Observed type | Example |
| --- | --- | --- |
| `count` | `integer` | 1 |
| `fetched_at` | `string` | 2026-09-24T08:48:44Z |
| `filter` | `string` | dining |
| `pagination` | `object` | 4 fields |
| `pagination.has_more` | `boolean` | true |
| `pagination.next_page` | `integer` | 2 |
| `pagination.page` | `integer` | 1 |
| `pagination.total_pages` | `integer` | 523 |
| `res_id` | `string` | 18439027 |
| `restaurant_id` | `string` | 18439027 |
| `reviews` | `array` | 1 items |
| `reviews` | `array` | 1 items |
| `sort` | `string` | newest |

## Execution behavior

A `200` response completed inline. A `202` response was queued; poll `GET /jobs/{id}` until the job reaches `completed` or `failed`. Use an `Idempotency-Key` when retrying must not create a duplicate logical job.

## Related documentation

- [Authentication](https://docs.upscrape.com/docs/api/authentication)
- [Jobs and results](https://docs.upscrape.com/docs/api/jobs)
- [Errors and retries](https://docs.upscrape.com/docs/api/errors)
- [Idempotency](https://docs.upscrape.com/docs/api/idempotency)