# The legacy Content API stops working

Calls to /api/v1/* on Tripadvisor Content API stopped working on August 31, 2026.

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.

## What to use instead

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.

- API: Tripadvisor Content API (api.content.tripadvisor.com)
- Kind: Removal
- Takes effect: August 31, 2026
- Calls after that day: fail
- Calls it hits: `/api/v1/*`
- Source: [Announcement](https://docs.terra.tripadvisor.com/docs/faq)
- Verified: November 6, 2026, against Tripadvisor Content API's own pages
- Page: https://www.okapi.bot/providers/tripadvisor-content-api/breaking-changes/the-legacy-content-api-stops-working/

## Tripadvisor Content API's words

> The legacy Content API will be sunset and API keys deprecated on August 31, 2026

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent