Tripadvisor restaurants in a city
Restaurants in a city or region as Tripadvisor lists them, 30 per page (plus sponsored listings): name, id, URL, rating, review count, cuisines, establishment types, price level, open status and weekly hours, award, menu link, reservation and delivery options, address, phone, coordinates, photo and review snippets, with raw. total and the available filters (cuisines, meals, diets, price, features, neighborhoods ...) come with the list. Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
locationrequired | string | City or region: a Tripadvisor geo id (187147), g187147, a Tripadvisor URL containing g<id>, or a place name (the first matching city or region is used; location.resolved_from echoes it). Example: 187147 |
filters | string | Site filter tokens from Tripadvisor list URLs, comma-separated (max 6), e.g. c10591 (establishment / cuisine), zfp58 (dining option), zft10640 (tag). |
page | integer | Page number (30 per page). Pass next_page back as page; null on the last page. Example: 1 |
domain | com | co.uk | de | fr | it | es | in | Tripadvisor market: com (default), co.uk, de, fr, it, es or in. Names, prices, currency and review translations follow the market. Default: com |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/tripadvisor/v1/restaurants?location=187147" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/tripadvisor/v1/restaurants",
params={"location": "187147"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/tripadvisor/v1/restaurants");
url.searchParams.set("location", "187147");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); 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).