Tripadvisor Scraper API

A Tripadvisor scraper API that takes a destination name — “Rome, Italy”, “New York City” — and returns its restaurants or hotels: name, rating, review count, price level, cuisines, full address, phone, coordinates and the detail URL. The destination is resolved to Tripadvisor’s own geo id for you, so there is no listing URL to hunt down first.

By Aldo Morese, founder of QuanticData · Published Aug 21, 2026 · Updated Sep 3, 2026

Get my free API key See the request

$0.001 per delivered place · $2 free every month · Failed runs never billed

POST /v1/scraper/collectors/tripadvisor_search/run

$ curl $QD/tripadvisor_search/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{"location": "New York City", "type": "restaurants", "max_results": 60}'
{ "status": "done", "count": 60,
  "results": [
    {
      "id": "…",
      "name": "…",
      "type": "…",
      "rating": … } ],
  "cost": 0.06 }
# 60 places × $0.001 · nothing delivered, nothing charged

Tripadvisor Scraper API: location and type in, a residential exit in the middle, delivered rows with rank, id and name on the right, $0.001 per place. — You send location and type; the run goes out through a residential exit and comes back as places with rank, id and name — 14 fields on every row — and you are billed $0.001 for each place actually delivered, nothing for a run that delivers none.

$0.001 / place2,000 places on the free $2 every month

Semantic inputlocation, type, country — no URL lists

Up to 300places per run, pagination handled for you

No browserread over HTTP/TLS — cheaper and faster than rendering

Try it

Tripadvisor listings, running now

Change the input and run it against the live collector — nothing to install, no sign-up.

Run it from your own code, on your own inputs

Same collector, same rows — $2 of free API credit every month, no card.

Get my free API key

What a Tripadvisor scraper API does

Every Tripadvisor listing URL is keyed by a numeric geo id nobody knows by heart, so the first thing this collector does is what the site’s own search box does: one cheap JSON call to the typeahead that turns a destination name into that id and its slug. The slug is taken from the URL Tripadvisor returns rather than derived from the name, because the rule for which parts survive — “Rome, Lazio, Italy” becomes Rome_Lazio — is theirs, not ours.

The rows then come from the schema.org ItemList Tripadvisor server-renders for search engines, not from the visible cards. That block is better on three counts: names arrive already decoded (O’Hara’s, not an entity), sponsored placements are excluded by the source itself, and it survives the CSS churn that breaks class-based parsers. The DOM is deliberately not used even as a fallback — its rating hooks are not scoped to a card, so on a hotel page the top carousel’s rating would be delivered as row 1’s. Every field was confirmed populated on 30 of 30 rows of both listing types. Tripadvisor sits behind DataDome; this reads on a residential exit without a browser, which keeps it a cheap fetch.

Limits, in plain numbers

Everything that bounds one run of this collector. No hidden throttles.

Max per run

300 places

Price

$0.001 / place

Per 1,000

$1.00

Failed runs

Free zero rows, zero charge

Free every month

$2 no card

Rate limit

60 req/min on the free tier

What one place looks like

Every delivered place carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

Field	Type	What it holds
`rank`	integer	Position in Tripadvisor's order for this response. Tripadvisor re-ranks between requests, so this is not a stable property of the place.
`id`	string · nullable	Tripadvisor location id.
`name`	string	Place name.
`type`	string	"restaurant" or "hotel".
`rating`	number · nullable	Average rating out of 5.
`reviews`	integer · nullable	Number of reviews.
`price_level`	string · nullable	Price band as Tripadvisor states it ($$ - $$$ for restaurants, a currency tier for hotels). Not a nightly rate.
`cuisines`	string[] · nullable	Cuisine tags (restaurants only).
`address`	string · nullable	Full address on one line.
`latitude`	number · nullable	GPS latitude.
`longitude`	number · nullable	GPS longitude.
`phone`	string · nullable	Phone number as published.
`url`	string · nullable	Canonical detail page URL.
`image`	string · nullable	Thumbnail URL.

Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

Input	Type	Required	What it does
`location`	string	yes	City or area, e.g. "New York City" or "Rome, Italy". Resolved through Tripadvisor's own destination lookup; the resolved name is reported in the run notes.
`type`	string	no	Restaurants or hotels for that destination. One of: `restaurants`, `hotels`.
`country`	string	no	ISO 3166-1 alpha-2 code — proxy exit geo and Google locale (gl). Omit for the default pool.
`max_results`	integer	no	How many places to deliver at most (1–300). You pay only for delivered places.

Pricing

Tripadvisor Scraper API pricing

$0.001 per delivered place. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 2,000 places before you spend anything.

$0.001per delivered place$1 per 1,000 delivered places

2,000 placeson the free allowance$2 every month, no card

Zero rowszero chargeblocks, captchas and retries are on us

−30%on volume tiersthe catalog returns your key's price

Pay as you go

$0/mo

$2 free credit / month
60 requests / min
List unit prices

Starter

$19/mo

$15 free credit / month
300 requests / min
10% off unit prices

Growth

$79/mo

$50 free credit / month
600 requests / min
20% off unit prices

Scale

$299/mo

$250 free credit / month
1,200 requests / min
30% off unit prices

Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.

Integration

One POST, typed rows

Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/scraper/collectors/tripadvisor_search/run.

curl -X POST https://api.quanticdata.io/v1/scraper/collectors/tripadvisor_search/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"location":"New York City","type":"restaurants","max_results":60}'

import requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/tripadvisor_search/run",
    headers={"Authorization": f"Bearer {QD_API_KEY}"},
    json={
        "location": "New York City",
        "type": "restaurants",
        "max_results": 60
    },
    timeout=120,
)
for row in r.json()["payload"]["results"]:
    print(row)

const res = await fetch(
  "https://api.quanticdata.io/v1/scraper/collectors/tripadvisor_search/run",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.QD_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({"location":"New York City","type":"restaurants","max_results":60}),
  },
);
const { payload } = await res.json();
console.table(payload.results);

claude mcp add quanticdata \
  -e QUANTICDATA_API_KEY=qd_live_your_key_here \
  -- npx -y quanticdata-mcp

# then, in the chat:
> run the tripadvisor_search collector with location="New York City" and type="restaurants"

What people build with the Tripadvisor scraper API

Three shapes of work this endpoint was designed around.

Destination benchmarking

The restaurant or hotel set of a city with rating, review count and price level on every row — the shape a market-entry or tourism-board study starts from.

Local lead lists

Address, phone and coordinates per venue, deduplicated by Tripadvisor’s id, ready to join with Google Maps rows for the same businesses.

Rating monitoring

Re-run a destination monthly and diff by id: new venues, closed ones, and rating and review-count movement per venue.

Tripadvisor Scraper API versus rolling your own

The differences that actually cost time when you build this in-house.

	DIY scraper	This collector
Finding the listing	A geo id you look up by hand	A destination name, resolved through Tripadvisor’s own typeahead
Sponsored rows	Mixed into the cards	Excluded by the source block itself
Ratings	Unscoped hooks that hand row 1 the carousel’s rating	Per-item values from the ItemList, checked on 30/30 rows
Anti-bot	DataDome blocks a datacenter fetch	Residential exit, no browser, failed runs free

What people search for

Live autocomplete demand around Tripadvisor listings, pulled with our own Keyword ideas collector.

Tripadvisor Scraper API: the POST to /v1/scraper/collectors/tripadvisor_search/run with location and type on the left, and the JSON envelope on the right with 60 places and usage.cost_usd $0.06. — The same call you would paste into a terminal: a Bearer key, location, type and country in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many places arrived and usage.cost_usd is $0.06, which is 60 × $0.001. A run that delivers nothing costs nothing. The key is good for 60 req/min on the free tier.

Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

FAQ

Questions we get about the Tripadvisor scraper API.

Something else? Ask us →

Does Tripadvisor have an official API?

Tripadvisor offers a paid Content API to approved partners, with its own terms and limits. This collector reads the public listing pages instead and needs nothing from Tripadvisor — a destination name is the whole input.

Restaurants or hotels?

Either: set type to restaurants or hotels. The row shape is the same and type is stated on every row.

Does it return the reviews themselves?

No — it returns the listings with their rating and review count. Review text lives on the venue page, which is a different surface from the search listing this reads.

Why not read the cards as a fallback when the ItemList is missing?

Because the DOM’s rating and review hooks are not scoped to a card: on a hotel page an unscoped read returns 54 nodes, carousel first, so row 1 would get the wrong rating. A wrong number that looks right is worse than a reported miss, so a page without the ItemList is reported, not guessed.

Is there a free Tripadvisor scraper API?

Every account gets $2 of credit every month with no card, which is about 2,000 delivered places on this endpoint at $0.001 each. It renews monthly, and a run that delivers nothing is never billed — so a failed or blocked attempt does not eat the allowance.

How much does one run cost?

Multiply the rows you actually receive by $0.001. A run capped at 300 places — the maximum for this collector — costs $0.3 if every row comes back, and less when the source has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.

Run the Tripadvisor scraper API now

$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.

Get my free API key