Tripadvisor Content API
legacy Content API removal
Stopped workingSubscribe to Tripadvisor Content APIShare
The legacy Tripadvisor Content API was sunset on August 31, 2026. Calls to /api/v1/* fail since that day, and legacy API keys were deprecated. Requests sent to the host are no longer supported.
Calls it hits
/api/v1/*
What to use instead of these calls
Sign up for Terra Discover to generate a Terra API key, then call the new endpoints /locations/{id}, /locations/{id}/photos, /locations/{id}/reviews, or /geos/{id} with version=1. Moving involves more than updating credentials, as Terra is a new product requiring a new account, new terms, and usage-based pricing instead of the free tier.
Terra is a new product: a new account, a new key, new terms and usage-based pricing replacing the free tier.
In Tripadvisor Content API's words
The legacy Content API will be sunset and API keys deprecated on August 31, 2026
Facts
- API
- Tripadvisor Content API
api.content.tripadvisor.com - Kind
- Removal
- Takes effect
- August 31, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Tripadvisor Content API's own pages
Questions
When does this change take effect?
Calls to /api/v1/* on Tripadvisor Content API stopped working on August 31, 2026.
What happens to calls after August 31, 2026?
They have failed since August 31, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.