Tripadvisor Content API
"Access reviews, photos, and more from 8 million locations worldwide." [1]
The Tripadvisor Content API provides access to reviews, photos, location details, and search across more than 8 million hotels, restaurants, and attractions worldwide, targeting consumer-facing travel apps and destination marketing products. Pricing is usage-based at $0.015 per 1,000 billable entities, with a free tier of 1,000 lifetime billable entities on the current Terra platform, and an enterprise plan available. The API uses REST with API key auth, supports self-serve signup, and offers an MCP server. Notable restrictions apply: content caching and storage are prohibited, Tripadvisor attribution is required, and use is limited to B2C products, excluding reputation management tools and academic research.
Best for / Avoid if
Best for: Prototypes and side projects - free to start, no sales call; AI agents and automation - an agent-ready surface (MCP / llms.txt); Cost-sensitive teams - low, transparent entry price
Avoid if: You have strict compliance requirements
Scores
- 30 / 100Agent friendliness
- 100 / 100Pricing transparency
- 70 / 100Setup speed
- 0 / 100Docs quality
- 100 / 100Procurement ease
- 0 / 100Trust readiness
Pricing & procurement
- Pricing model
- Usage-based [2]
- Published pricing
- ✓ Yes [3]
- Free tier
- ✓ Yes [4]
- Free tier details
- Legacy Content API: 5,000 API calls/month free (recurring, credit card required for overages). Terra platform: first 1,000 billable entities per account free (one-time lifetime allowance, not recurring). [5]
- Self-serve signup
- ✓ Yes [6]
- Requires sales call
- ✗ No
- Enterprise plan
- ✓ Yes [7]
| Plan | Item | Per | Amount | Source |
|---|---|---|---|---|
| Terra Discover (usage-based) | Billable entities (locations returned), tier 1 | billable entity (1–1,000/month) | $0.015 | source |
| Terra Discover (usage-based) | Billable entities, tier 2 | billable entity (1,001–2,000/month) | $0.0135 | source |
| Terra Discover (usage-based) | Billable entities, tier 3 | billable entity (2,001–3,000/month) | $0.0122 | source |
| Terra Discover (usage-based) | Billable entities, tier 4 | billable entity (3,001–4,000/month) | $0.0109 | source |
| Terra Discover (usage-based) | Billable entities, tier 5 | billable entity (4,001–5,000/month) | $0.0098 | source |
| Terra Discover (usage-based) | Billable entities, tier 6 (floor rate) | billable entity (5,001+/month) | $0.009 | source |
| Legacy Content API (free tier) | Monthly free allowance | first 5,000 API calls/month | $0 | source |
| Terra Discover (lifetime free allowance) | One-time free allowance (new accounts) | first 1,000 billable entities (account lifetime) | $0 | source |
Capabilities
- Supported actions
- location_search, nearby_location_search, location_details, location_photos, location_reviews, agentic_search [8]
- Regions
- global, 8+ million locations worldwide
- Languages
- 29 languages supported
- Input types
- text query, location ID, lat/lon + radius, category filter, address, phone number
- Output types
- JSON
- Webhooks
- ✗ No
- Sandbox / test mode
- ✗ No [9]
- SDK languages
- Unknown
- MCP server
- ✓ Yes [10]
Trust & compliance
- SOC 2
- – Unknown
- HIPAA
- – Unknown
- GDPR
- – Unknown [11]
- ISO 27001
- – Unknown
- PCI DSS
- – Unknown
- Published SLA
- ✗ No [12]
- Rate limits
- 50 queries per second (QPS) across all endpoints; Search APIs: up to 10,000 calls per day; rate limits use a 24-hour rolling window starting with the first call made [13]
- Known restrictions
- Caching, storing or indexing is not permitted for any content except Location ID attribute, Must credit Tripadvisor when using the Locations API product, Must use bubble ratings provided in API response; no custom rating icons, May only quote from a 5-bubble rave review if the overall property rating is at least 4 out of 5, When referencing a property's popularity ranking, must cite the specific month and year, Content intended for B2C consumer-facing websites and apps only; reputation management tools, B2B products, and academic research are excluded, Vacation rental content not available, One API key per account, Contact sales for usage exceeding 500,000 calls monthly (legacy Content API), All proposed integrations must be sent to Tripadvisor for approval to ensure display requirements are met [14]
Integration
- API style
- rest
- Base URL
- https://api.content.tripadvisor.com/api/v1/
- Version
- v1
- Versioning
- url
- Stability
- ga
- Auth methods
- api_key
- Error format
- problem+json
- Rate limit
- 50 / second
Other Places & POI APIs
Azure Maps Search (POI)
"Azure Maps is a collection of geospatial services and SDKs that use fresh mapping data to provide geographic context to web and mobile applications."
Google Places API
"The Places API is a service that accepts HTTP requests for location data through a variety of methods. It returns formatted location data and imagery about establishments, geographic locations, or prominent points of interest."
TomTom Search / Places API
"Search is a RESTful API designed for developers allowing single-line fuzzy search for addresses and POIs. Search assigns a latitude/longitude to a specific address, cross street, geographic feature, or point of interest (POI)."
Radar Geocoding API
"Use Radar's geocoding APIs to convert addresses to latitude and longitude coordinates, or vice versa."
Mapbox Search Box API
"All-in-one location search for addresses, places, and points of interest"
HERE Geocoding & Search API (Discover & Browse)
"Enable precise conversion and discovery of geocoordinates, POIs and addresses to improve location accuracy and context."
References
- ↑Description: tripadvisor.com
- ↑Pricing model: tripadvisor-content-api.readme.io · docs.terra.tripadvisor.com
- ↑Published pricing: docs.terra.tripadvisor.com · docs.terra.tripadvisor.com
- ↑Free tier: docs.terra.tripadvisor.com · tripadvisor-content-api.readme.io
- ↑Free tier details: docs.terra.tripadvisor.com · tripadvisor-content-api.readme.io
- ↑Self-serve signup: tripadvisor-content-api.readme.io
- ↑Enterprise plan: docs.terra.tripadvisor.com · tripadvisor-content-api.readme.io
- ↑Supported actions: tripadvisor-content-api.readme.io · docs.terra.tripadvisor.com
- ↑Sandbox: tripadvisor-content-api.readme.io
- ↑MCP server: docs.terra.tripadvisor.com · docs.terra.tripadvisor.com
- ↑GDPR: tripadvisor.com
- ↑Published SLA: tripadvisor-content-api.readme.io
- ↑Rate limits: tripadvisor-content-api.readme.io · tripadvisor-content-api.readme.io · tripadvisor-content-api.readme.io
- ↑Known restrictions: tripadvisor-content-api.readme.io · tripadvisor-content-api.readme.io · tripadvisor-content-api.readme.io
Change history
- 2026-06-14 Robots Allows Agents: (none) → No
- 2026-06-14 Capabilities: {} → {"nearby":true,"photos":true,"reviews":true,"poi_search":true,"place_details":t…
- 2026-06-14 Summary Md: (none) → The Tripadvisor Content API provides access to reviews, photos, location detail…
- 2026-06-14 Score Docs Quality: (none) → 0
- 2026-06-14 Score Procurement Friction: (none) → 100
- 2026-06-14 Score Trust Readiness: (none) → 0
- 2026-06-14 Score Agent Friendliness: (none) → 30
- 2026-06-14 Avoid If: (none) → You have strict compliance requirements
- 2026-06-14 Scoring Methodology: (none) → Scores are computed deterministically from this profile's published, sourced fi…
- 2026-06-14 Best For: (none) → Prototypes and side projects - free to start, no sales call, AI agents and auto…
- 2026-06-14 Score Pricing Transparency: (none) → 100
- 2026-06-14 Score Setup Speed: (none) → 70
- 2026-06-14 Input Types: set to text query, location ID, lat/lon + radius, category filter, address, phone numb…
- 2026-06-14 Output Types: set to JSON
- 2026-06-14 SDK Packages: set to (none)
- 2026-06-14 MCP Server Available: set to Yes
- 2026-06-14 Pricing Model: set to usage_based
- 2026-06-14 Has Published Pricing: set to Yes
- 2026-06-14 Free Tier Available: set to Yes
- 2026-06-14 Free Tier Details: set to Legacy Content API: 5,000 API calls/month free (recurring, credit card required…
- 2026-06-14 Self Serve Signup: set to Yes
- 2026-06-14 Requires Sales Call: set to No
- 2026-06-14 Enterprise Plan Available: set to Yes
- 2026-06-14 SLA Published: set to No
- 2026-06-14 Documented Rate Limits: set to 50 queries per second (QPS) across all endpoints; Search APIs: up to 10,000 cal…
- 2026-06-14 Rate Limit Requests: set to 50
- 2026-06-14 Rate Limit Window: set to second
- 2026-06-14 Known Restrictions: set to Caching, storing or indexing is not permitted for any content except Location I…
- 2026-06-14 Auth Methods: set to api_key
- 2026-06-14 Auth Docs URL: set to https://tripadvisor-content-api.readme.io/reference/authentication
- 2026-06-14 API Style: set to rest
- 2026-06-14 Base URL: set to https://api.content.tripadvisor.com/api/v1/
- 2026-06-14 API Version: set to v1
- 2026-06-14 Versioning Scheme: set to url
- 2026-06-14 Stability: set to ga
- 2026-06-14 MCP URL: set to https://docs.terra.tripadvisor.com/mcp
- 2026-06-14 Quickstart URL: set to https://www.tripadvisor.com/developers
- 2026-06-14 Webhooks Supported: set to No
- 2026-06-14 Requires Verification: set to Yes
- 2026-06-14 Starting Price Usd: set to 0.015
- 2026-06-14 Price Basis: set to 1,000 billable entities
- 2026-06-14 Free Tier Limit: set to 5,000 calls/month (legacy Content API); 1,000 billable entities lifetime (Terra)
- 2026-06-14 Notable Customers: set to (none)
- 2026-06-14 Fields Not Found: set to soc2, hipaa, iso_27001, pci_dss, minimum_commitment, exact list of 29 supported…
- 2026-06-14 Source Confidence: set to high
- 2026-06-14 Extractor: set to claude-subagent:sonnet
- 2026-06-14 Last Verified At: set to 2026-06-14T00:00:00.000Z
- 2026-06-14 Status: set to published
- 2026-06-14 Error Format: set to problem+json
- 2026-06-14 Sandbox Available: set to No
Suggest an edit / leave a review
Leave a review or comment
curl -X POST https://apio.sh/api/feedback/tripadvisor-content \
-H 'Content-Type: application/json' \
-d '{"kind":"review","rating":5,"body":"Your experience with this API…"}'Suggest a correction to a field (cite a source)
curl -X POST https://apio.sh/api/suggest/tripadvisor-content/FIELD \
-H 'Content-Type: application/json' \
-d '{"value":"corrected value","citations":[{"url":"https://source.example/page","excerpt":"supporting quote"}],"note":"what changed and why"}'