GET

OpenTable Restaurant Reviews API

Get normalized guest reviews for an OpenTable restaurant, ordered by date or rating and paginated up to 25 reviews per call.

Overview

Newest by default

Reviews are returned newest-first unless you select highest or lowest. Pages are 1-indexed and page_size defaults to the maximum of 25.

Use the stable restaurant_id returned by OpenTable Restaurant Search. Each review includes overall, food, service, ambience, and value ratings; reviewer details; dining and submission times; verification; helpfulness; and reviewer-uploaded photos when available.

Endpoint URL

GET https://api.stayapi.com/v1/opentable/restaurant/reviews

Query Parameters

Parameter	Type	Required	Description
restaurant_id	integer	Required	Positive OpenTable restaurant ID, available from Restaurant Search.
sort	string	Optional	`newest` (default), `highest`, or `lowest`.
page	integer	Optional	1-indexed page number. Default: `1`.
page_size	integer	Optional	Reviews per page, from 1 to 25. Default and maximum: `25`.

Sorting

newest

Most recently submitted reviews first. This is the default.

highest

Highest overall rating first.

lowest

Lowest overall rating first.

Response Format

Pagination

total_count is the restaurant's total review count.
total_pages reflects the selected page size.
has_more is true when another page is available.
sort echoes the normalized sort value used for the request.

Review field	Description
id, text	Stable review ID and the guest's review text.
ratings	Overall, food, service, ambience, value, and normalized noise level.
reviewer	Name, initials, location, approved review count, and VIP status when available.
dined_at, submitted_at	ISO 8601 dining and submission timestamps.
verified	True when OpenTable marks the review as verified.
helpfulness	Up votes, down votes, and score.
photos	Reviewer photos with caption and nullable CDN URLs for five sizes.

Sparse fields stay predictable

Optional upstream values are returned as null, while photos is always an array. Your client can keep one response shape across restaurants.

Error Responses

Errors follow RFC 7807 Problem Details. OpenTable review failures include provider: "opentable" and product: "reviews".

400 Invalid sort

INVALID_SORT when sort is not newest, highest, or lowest.

422 Validation error

Missing or invalid restaurant_id, page, or page_size, including page sizes above 25.

502 Upstream error

UPSTREAM_ERROR when OpenTable does not return a usable response after retries.

Best Practices

Use newest for incremental collection and stop when you reach a review already stored.
Follow has_more instead of guessing how many pages remain.
Keep the same sort value while paging to preserve a consistent ordering.
Use highest and lowest for targeted sentiment samples.

Related Endpoints

Restaurant Search

Find restaurants and obtain the ID required by this endpoint.

View Documentation →

Private Dining

Find venues with event contacts and capacity details.

View Documentation →

Request

curl -X GET "https://api.stayapi.com/v1/opentable/restaurant/reviews?restaurant_id=404046&sort=newest&page=1&page_size=25" \
  -H "X-API-Key: YOUR_API_KEY"

const params = new URLSearchParams({
  restaurant_id: '404046',
  sort: 'newest',
  page: '1',
  page_size: '25'
});

const response = await fetch(
  `https://api.stayapi.com/v1/opentable/restaurant/reviews?${params}`,
  { headers: { 'X-API-Key': 'YOUR_API_KEY' } }
);

if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(`${data.reviews.length} of ${data.total_count} reviews`);

import requests

response = requests.get(
    "https://api.stayapi.com/v1/opentable/restaurant/reviews",
    params={
        "restaurant_id": 404046,
        "sort": "newest",
        "page": 1,
        "page_size": 25,
    },
    headers={"X-API-Key": "YOUR_API_KEY"},
)
response.raise_for_status()
data = response.json()
print(f"{len(data['reviews'])} of {data['total_count']} reviews")

<?php
$params = http_build_query([
    'restaurant_id' => 404046,
    'sort' => 'newest',
    'page' => 1,
    'page_size' => 25,
]);

$ch = curl_init("https://api.stayapi.com/v1/opentable/restaurant/reviews?{$params}");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ['X-API-Key: YOUR_API_KEY']);
$response = curl_exec($ch);
$data = json_decode($response, true);
curl_close($ch);

echo count($data['reviews']) . " reviews returned\n";

require 'net/http'
require 'json'

uri = URI('https://api.stayapi.com/v1/opentable/restaurant/reviews')
uri.query = URI.encode_www_form(
  restaurant_id: 404046,
  sort: 'newest',
  page: 1,
  page_size: 25
)

request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'YOUR_API_KEY'
response = Net::HTTP.start(uri.host, uri.port, use_ssl: true) { |http| http.request(request) }
data = JSON.parse(response.body)
puts "\#{data['reviews'].length} of \#{data['total_count']} reviews"

Response

{
  "success": true,
  "restaurant_id": 404046,
  "total_count": 80,
  "page": 1,
  "page_size": 25,
  "total_pages": 4,
  "has_more": true,
  "sort": "newest",
  "reviews": [
    {
      "id": "OT-404046-3819-180028644728",
      "text": "Enjoyed our meal very much.",
      "ratings": {
        "overall": 5,
        "food": 5,
        "service": 5,
        "ambience": 5,
        "value": 4,
        "noise": "moderate"
      },
      "reviewer": {
        "name": "Nancy",
        "initials": "N",
        "location": "Calgary",
        "review_count": 11,
        "is_vip": null
      },
      "dined_at": "2026-07-02T18:30:00+02:00",
      "submitted_at": "2026-07-05T10:39:45Z",
      "verified": true,
      "from_previous_concept": false,
      "helpfulness": { "up": 0, "down": 0, "score": 0 },
      "photos": []
    }
  ]
}

{
  "type": "https://api.stayapi.com/errors/invalid-sort",
  "title": "Invalid Sort",
  "status": 400,
  "detail": "sort must be one of: newest, highest, lowest",
  "instance": "/v1/opentable/restaurant/reviews",
  "provider": "opentable",
  "product": "reviews",
  "error_code": "INVALID_SORT",
  "correlation_id": "request-id"
}