Tripadvisor hub

Tripadvisor Restaurants API

The restaurants in a city or region with cuisines and price level, in the site's order.

GET /v1/tripadvisor/restaurants

1 credit Failed requests are free A not-found answer is still charged

About this endpoint

GET /v1/tripadvisor/restaurants lists the restaurants in a city or region. geoId is the city's geo id: the g number in a Tripadvisor address, or the locationId of a geo match from search (60763 is New York City).

data.totalCount counts the restaurants as the site does. The site's list stops at 10,000 places (New York City has more), and data.truncated is true when paging ends before totalCount. data.places holds this page's, in the site's own order with sponsored places left out. Each carries locationId (pass it to the restaurant and restaurant reviews routes), name, url, rating, reviewCount, ranking, cuisines, priceRange ($$ - $$$), coordinates, address, image and award. Pass page.nextCursor back as cursor while page.hasMore is true.

Price

From $1.35 per 1,000 requests

1 credit per request. Failed requests are free.

Scale pack
$1.64 / 1,000
Growth pack
$2.36 / 1,000

The lowest rate is on annual plans; packs are pay as you go.

Example request

Send your API key in the x-api-key header. New accounts get 100 free credits, no card needed.

Request
cURL

Example response

A 200 response. Live responses have the same shape with current data.

Request
JSON

Tripadvisor Restaurants API FAQ

Where do I find a city's geo id?

It is the g number in any Tripadvisor address for the city (Restaurants-g60763-New_York_City… is 60763), or the locationId of a geo match from GET /v1/tripadvisor/search?type=geo.

Can I filter by cuisine or price?

Not in the request. Every row carries cuisines and priceRange, so filter the pages you collect.

What does a geo id that does not exist return?

HTTP 200 with data.lookupStatus not_found and an empty list. Check lookupStatus before storing rows.

How many credits does a call cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth. Each paginated page is a separate billed request.