The API Report CardAPI Index
TripAdvisor

TripAdvisor API

Travel & Hospitality / Reviews · tripadvisor.com

Tripadvisor's Content API serves location search, details, photos, and reviews via a self-serve key, 5,000 free calls a month then pay as you go. Production approval needs a working site and card on file. Connectivity APIs for hotel supply are partner-gated, and a Terra transition looms.

Last verified: July 2026Hospitality & Travel
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODContent API on readme.io plus partner-gated Connectivity APIs for hotel availability and instant booking.
AccessGOODSelf-serve key with 5,000 free calls a month; approval checks your site, and heavy volume goes through sales.
CoverageGOODSearch, details, photos, and reviews across 7.5M locations; only 5 reviews and 5 photos per location.
AuthGOODSingle API key issued after signup with a billing card on file; passed on each request.
Docs & DXGOODCurrent Content API reference on readme.io; older connectivity docs are scattered, SDKs mostly community-built.
StabilityMIXEDThe Content API is flagged as superseded by a coming Terra API with unclear migration timing; partners are unsure what to build against.
Supergood: TripAdvisor shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

TripAdvisor scores A on the API Report Card. Tripadvisor's Content API serves location search, details, photos, and reviews via a self-serve key, 5,000 free calls a month then pay as you go. Production approval needs a working site and card on file. Connectivity APIs for hotel supply are partner-gated, and a Terra transition looms.

Tried to integrate with TripAdvisor?
SOURCES
Content API access application slow and opaque - developers report weeks with no response or rejection without clear reason; sites without working URLs/traffic auto-rejected tripadvisor.com
'Access Denied' and 'User is not authorized to access this resource' errors common even with valid keys, especially for connectivity endpoints tripadvisor.com
Only 5 reviews and 5 photos per location returned via Content API - insufficient for many use cases, drives developers to scraping or third-party data resellers tripadvisor-content-api.readme.io
Strict display/attribution requirements (must show logo, bubble images, link back) constrain UX and are enforced via TOS audits developer-tripadvisor.com
Documentation fragmented across developer-tripadvisor.com (legacy/marketing), tripadvisor-content-api.readme.io (current Content API), Viator docs.viator.com, and HTNG/partner-only spec sites developer-tripadvisor.com
Current Content API platform flagged as being superseded by a 'Terra API' platform - migration timing unclear, partners unsure which to build against developer-tripadvisor.com
One API key per account; high-volume partners must contact sales, no programmatic key/scoping system tripadvisor-content-api.readme.io
Connectivity APIs (Hotel Availability Check, Instant Booking, Review Express) are partner-gated through a small set of certified channel managers/booking engines - direct hotel integrations difficult developer-tripadvisor.com
Third-party scraping/reseller ecosystem (DataForSEO, Apify, Bright Data, OpenWeb Ninja, Wextractor) flourishes precisely because official API is restrictive on review depth/volume dataforseo.com
Long-standing accusations of fake/incentivized reviews and inadequate moderation; UK ASA and consumer-protection scrutiny theguardian.com
Owners report difficulty getting clearly fake or extortion-style negative reviews removed; flagging process slow and opaque tripadvisor.com
Tripadvisor Ads (Business Advantage / sponsored placements) seen as expensive with unclear ROI by small independent hotels hotelmanagement.net
Viator pricing on the consumer side often higher than booking directly with the tour operator; commission spread complaints from operators reddit.com
Customer support for both consumers and business owners frequently rated poor - automated responses, hard to reach humans trustpilot.com
Defamation lawsuits and content-removal disputes (hotel owners suing reviewers/Tripadvisor over alleged false reviews) bbc.com
Declining organic traffic and rankings as Google Hotels/Things to do push Tripadvisor down SERPs; ongoing antitrust commentary skift.com
Brand confusion across Tripadvisor / Viator / TheFork after the 2023-2025 restructuring; unclear which property a traveler is transacting on phocuswire.com