https://api.sandbase.ai/v1/api/opentable/reviewsGet diner reviews for a restaurant on OpenTable by restaurant ID, with overall and sub-ratings, text, date and diner info.
Your output will appear here
Complete the inputs, then click Run.
Get diner reviews for a restaurant on OpenTable by restaurant ID, with overall and sub-ratings, text, date and diner info.
curl -X POST "https://api.sandbase.ai/v1/api/opentable/reviews" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"rid": "r/central-park-boathouse-new-york-2"}'
The result is returned in outputs[0].data as structured JSON.
| Name | Type | Required | Description |
|---|---|---|---|
rid | string | Yes | Parameter defines the OpenTable Restaurant ID. This identifier can be found in the URL of the restaurant's page, it's the path of the URL (the part after the first singular /). For example, in the URL `https://www.opentable.com/r/central- |
page | string | No | Parameter defines the page number. 1 (default) is the first page of 10 results, 2 is the 2nd page, etc. |
json_restrictor | string | No | Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details. |
$0.010 per successful call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/opentable/reviews" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"rid": "r/central-park-boathouse-new-york-2"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
ridstringrequiredParameter defines the OpenTable Restaurant ID. This identifier can be found in the URL of the restaurant's page, it's the path of the URL (the part after the first singular `/`). For example, in the URL `https://www.opentable.com/r/central-park-boathouse-new-york-2`, the Restaurant ID is `r/central-park-boathouse-new-york-2`.
pagestringParameter defines the page number. `1` (default) is the first page of 10 results, `2` is the 2nd page, etc.
json_restrictorstringParameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
OpenTable ReviewsThis API OpenTable | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/opentable/reviews with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: rid (string). Optional: page (string) and json_restrictor (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. OpenTable Reviews runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for OpenTable API access separately.