Search for Tripadvisor API pricing and you get two kinds of answer. One says the API is free and gives you 10,000 calls a day, which describes the old partner key, not the product you can sign up for today. The other prints a neat table of monthly tiers with round numbers that appear nowhere in Tripadvisor's own documentation. Neither helps a team that has to put a number in a budget.
This article works from the primary sources: the Tripadvisor Content API FAQ, its rate limit page, its caching policy and its Master Terms, all read on October 7, 2026. Where Tripadvisor does not publish a figure, we say so instead of guessing. Then we turn the rules into what a buyer actually pays per 1,000 reviews, and compare that with the routes review analytics teams use instead.
What the Tripadvisor Content API costs
Here is everything Tripadvisor states about the price in writing.
| Item | What Tripadvisor states |
|---|---|
| Free usage | The first 5,000 calls every month |
| Card on file | Required at signup, overage is charged to it |
| Billing model | Pay as you go, charged monthly |
| Rate per call | Not published, shown in a pricing chart at checkout and on the My Plans page |
| Volume discount | The rate falls as usage rises |
| Large accounts | Above 500,000 calls a month, contact sales |
| API keys | One per account |
| Cancellation | Any time, key stays active to the end of the billing cycle |
So the honest answer to how much the Tripadvisor API costs is: nothing for a small integration, and an amount you only see after you create an account and enter a card for anything larger. If someone shows you fixed monthly tiers, ask where they came from. The documentation also carries a banner announcing a newer platform called Terra, with its own docs and a signup portal still to come, so expect the commercial terms to move again.
The daily budget is the real meter
Tripadvisor does not sell you a plan. At signup you set a maximum daily budget, and that number becomes your daily call limit for the location details, photos and reviews endpoints. Calls past it get HTTP 429, Too Many Requests. The search endpoints have a separate fixed limit of 10,000 calls a day, and every key is capped at 50 queries per second.
One detail is worth knowing before you plan a batch job. The FAQ says daily limits reset at midnight UTC. The rate limit page says the window is a rolling 24 hours that opens with your first call and closes 24 hours later. Those are different behaviors, and a nightly job that runs at 23:30 UTC will see the difference. Build your scheduler to back off on 429 rather than trusting either clock.
Five reviews per call changes the unit price
The Location Reviews endpoint returns up to 5 of the most recent reviews for a location. Not 5 per page with a way to page further: 5, full stop. Ask again tomorrow and you get the 5 newest again, which overlap with yesterday's unless the property is busy.
That makes the usual per call math misleading. A hotel with 2,400 reviews costs one call and gives you 0.2 percent of its reviews. Getting the other 99.8 percent through the API is not expensive, it is impossible. For monitoring, 5 newest reviews are enough only if fewer than 5 new ones arrive between checks, which holds for a quiet restaurant and fails for a busy resort in season.
The no storage rule costs more than any fee
Tripadvisor's caching policy is one sentence long in effect: the location ID may be cached without limit, and all other attributes may not be cached, stored or indexed. The Master Terms add four more conditions that shape any product built on the API:
- Every page that shows Tripadvisor content must be made non indexable by search engines.
- You may not change the sort or ranking order, or be selective about which reviews you show.
- You may not show the content alongside other user generated content, or license similar content from another provider during the agreement (section 3.5.1).
- Tripadvisor's logo and bubble ratings must be served from Tripadvisor's own URLs.
Now cost the products buyers want. A rating trend by property needs stored ratings. A complaint analysis needs stored text. A reputation dashboard needs Google and Yelp next to Tripadvisor. A competitive set report needs history for hotels you do not own. The API license rules out all four at any price, which is why hotel groups and agencies end up reading the public pages with a Tripadvisor scraper API and keeping records under their own legal review.
Cost per 1,000 Tripadvisor reviews by route
To compare routes on one unit, we price 1,000 full reviews. A Tripadvisor hotel review page holds about 10 reviews, so 1,000 reviews take about 100 page requests on a page based tool. Marketplace and scraper prices come from each vendor's public page on October 7, 2026.
| Route | Price as listed | Per 1,000 reviews | Can you keep them |
|---|---|---|---|
| Tripadvisor Content API | 5,000 free calls, then an unpublished rate | Not available, 5 newest per location only | No |
| Apify Tripadvisor Reviews Scraper | From 0.90 USD per 1,000 reviews | 0.90 USD, lower on bigger Apify plans | Yes |
| Bright Data Tripadvisor scraper, pay as you go | 1.50 USD per 1,000 page loads | about 0.15 USD | Yes |
| WebScrap Starter | 49 USD for 50,000 pages | about 0.10 USD | Yes |
| WebScrap Growth | 149 USD for 250,000 pages | about 0.06 USD | Yes |
| WebScrap Scale | 499 USD for 1,500,000 pages | about 0.03 USD | Yes |
Two cautions on the page based rows. The 10 reviews per page holds for review pages; listing and search pages add requests that carry no review text, so a real job lands a little above these figures. And per review pricing, as on Apify, is easier to forecast when you do not know how deep each property's history goes. Our Apify pricing breakdown and Bright Data pricing breakdown cover the platform fees behind those two rows.
Real budgets compared
Here are four jobs we see hospitality buyers run, priced both ways. Daily checks read page one sorted by newest and only go deeper when a new review appears.
| Job | Tripadvisor Content API | Scraping API |
|---|---|---|
| 300 owned hotels, new reviews daily | About 9,000 calls, 4,000 above the free tier, nothing may be stored | 49 USD, about 9,000 pages, full history kept |
| Backfill 2,000 restaurants, 300 reviews each | Not possible | 149 USD for the month, about 60,000 pages |
| 5,000 hotel competitive set, daily rating trend | Ratings may not be stored, so no trend exists | 149 USD, about 150,000 pages |
| 25,000 locations for a reputation platform | Above 500,000 calls, sales quote, and no Google next to it | 499 USD, about 750,000 pages |
The page counts assume a page loads on the first try. Tripadvisor runs DataDome, and a plain HTTP request to a hotel page returned a 403 with a 775 byte JavaScript challenge when we tested it on October 7, 2026. A managed API retries those blocks through new residential addresses and bills only the successful fetch; the mechanics are on our DataDome bypass API page. Once new reviews arrive every morning, the work moves to the people who answer them, and routing each low rated review to the right general manager is a job for task assignment software rather than a shared inbox.
Where the Tripadvisor API is the right buy
Travel apps that display Tripadvisor to consumers. If your product shows a hotel's bubble rating and latest reviews to end users with Tripadvisor's branding, the Content API is built and licensed for exactly that, and many small apps never leave the free 5,000 calls.
Location matching. The search endpoints find the Tripadvisor location ID for a name or coordinates, and the ID is the one field you may cache forever. Even teams that collect public pages often use the API once to map their properties to the right IDs.
Small jobs with no monthly commitment. For a one off pull of a few thousand reviews, pay per use marketplace pricing beats any monthly plan, ours included. Bright Data's first 5,000 page loads a month are free, and 49 USD buys about 32,600 page loads at its pay as you go rate.
Everywhere else, which means stored history, analytics, full review text or several platforms in one view, a flat rate scraping API costs less and fits the use. The same arithmetic for Yelp is in our Yelp API pricing breakdown, and for Google on the Google Reviews API page.
Questions buyers ask
Is the Tripadvisor API free? The first 5,000 Content API calls each month are free. You still need to enter a credit card at signup, because anything above the free calls is charged to it at Tripadvisor's pay as you go rate, up to the daily budget you choose.
How much does the Tripadvisor API cost per call? Tripadvisor does not publish a per call rate. It shows a sliding volume price chart during checkout and on the My Plans page after signup, and the rate drops as usage grows. Above 500,000 calls a month, pricing goes through its sales team.
How many reviews does the Tripadvisor API return? Up to 5 of the most recent reviews per location, and up to 5 photos. There is no parameter to page further back, so older reviews are not reachable through the API at any price.
What is the Tripadvisor API rate limit? Your daily budget sets the daily call limit for location details, photos and reviews, with HTTP 429 above it. Search endpoints allow 10,000 calls a day, and every key is limited to 50 queries per second.
Can I store Tripadvisor API data in my database? Only the location ID. Tripadvisor's caching policy forbids caching, storing or indexing every other attribute, including ratings and reviews, and pages that show the content must be non indexable.
What is the cheapest way to get Tripadvisor reviews for analysis? For a one off pull, a pay per review marketplace scraper. For ongoing monitoring of hundreds of properties, a Tripadvisor review scraper API on a flat plan, where 49 USD buys 50,000 pages, roughly half a million reviews, and the records are yours to keep. Every plan is on the pricing page.