Tripadvisor API — FetchLayer Docs

Tripadvisor API v1

Find a hotel, restaurant or attraction by name, read its profile and traveller reviews, and page its photo gallery, from https://api.fetchlayer.dev/tripadvisor. Fast: a full profile comes back in a single request.

OpenAPI JSON

Tripadvisor API at a glance

This is the reference: every endpoint, its parameters and the fields it returns. The essentials first.

Returns
Hotels, restaurants and attractions, as typed JSON.
Endpoints
6 endpoints, grouped as Places, Reviews, Photos and Utility. See them all
Request
POST https://api.fetchlayer.dev/tripadvisor/<endpoint> with a JSON body.
Auth
Your FetchLayer API key as a Bearer token. One key works for every platform we support. Authentication
Cost
1 credit per page of results a call returns; the exact figure is on every response. Credits are $1.99 per 1,000 pay-as-you-go, plans start at $25 a month, and new accounts get 30 free requests.
MCP
Also on our MCP server for AI agents, with the same key and the same billing. Connect an agent

What teams use it for, with worked examples: Tripadvisor API

Available endpoints

Two ceilings worth knowing first

Reviews come 20 to a page, always. Asking for 200 in one page returns a byte-identical 20. Depth comes from pages and cursor, and each page walked bills as one request.

language is a translation target, not a filter. It changes the reported reviewCount without changing which reviews come back — Tripadvisor still serves a place's reviews in a mix of languages. Pair it with translate: true to get the text itself in that language, and read reviews[].originalLanguage to see what the reviewer actually wrote in.

Every response carries a notes[] array. It is where a truncated walk or an upstream limit gets reported, so a response can be well-formed and still incomplete. Read it before you treat a result as the whole story.

Product overview Tripadvisor API: what it returns, pricing and use cases