100 free credits — no credit card required.Start building
Logo
Back to blog

Best TripAdvisor Data APIs for Developers (2026): Pricing Compared

By Friday··15 min read

TripAdvisor's legacy Content API sunsets August 31, 2026. Here are the TripAdvisor data APIs compared on price and coverage, including the new self-serve Terra API and third-party options.

Best TripAdvisor Data APIs for Developers (2026): Pricing Compared

Big change in the TripAdvisor developer landscape this year: the legacy Content API is being retired. TripAdvisor has set the Content API to sunset on August 31, 2026, with the Partner API and Data Feeds following on October 30, 2026, and replaced them with a new self-serve Terra API. If you built on the old Content API, you have a migration on your hands, and if you are choosing now, the ground has shifted. This post compares the real ways to get TripAdvisor data in 2026, SocialCrawl first and argued honestly, with the official Terra successor and the third-party options that read public reviews without any signup.

Every price below was pulled from each vendor's live page and is stamped "pricing verified July 2026."

The best TripAdvisor data APIs at a glance

  1. SocialCrawl is best overall for public reviews and places in a unified schema, no signup approval
  2. TripAdvisor Terra API is the official successor, self-serve with attribution requirements
  3. DataForSEO is best cheapest per-review at scale
  4. Apify is best marketplace option for custom TripAdvisor scrapers
  5. Bright Data is best enterprise per-record infrastructure
  6. SerpApi is best if you already use it for other SERP data
APIBest forFree tierEntry paid priceAttribution required?
SocialCrawlUnified public reviews + places100 credits (never expire)£15 / 2,500 creditsNo
TripAdvisor TerraOfficial successor1,000 callsPay-as-you-go (rate at signup)Yes
DataForSEOCheapest per reviewn/a ($50 min top-up)~$0.075 / 1,000 reviewsNo
ApifyCustom scrapers$5 credit/mofrom $2.00 / 1,000 resultsNo
Bright DataEnterprise records5,000 page loads/mo$1.50 / 1,000 recordsNo
SerpApiExisting SerpApi users250 searches/mo$49/mo (5,000 searches)No

What makes a "best" TripAdvisor API in 2026?

  1. No approval queue. The old Content API framing was partner-gated; that is changing, and several third parties never gated at all. Time-to-first-call matters.
  2. Reviews and places coverage. Search for a location, then pull its traveler reviews with ratings, photos, and owner replies.
  3. Attribution and display terms. The official Terra API requires bubble ratings, review dates, and a credit on display. Third parties leave display compliance to you.
  4. Pricing model. Per credit, per call, per review, or per record, and how cheap it gets at volume.
  5. Schema. Does a TripAdvisor place come back in the same shape as your other data?

What does the response look like? One real call

A live SocialCrawl TripAdvisor search, unified schema (trimmed to one place):

curl "https://www.socialcrawl.dev/v1/tripadvisor/search?q=Eiffel%20Tower" \
  -H "x-api-key: $SOCIALCRAWL_KEY"
{
  "success": true,
  "platform": "tripadvisor",
  "endpoint": "/v1/tripadvisor/search",
  "data": {
    "items": [
      {
        "place": {
          "id": "d127002",
          "name": "Eiffel Tower Viewing Deck",
          "url": "https://www.tripadvisor.com/Attraction_Review-g45963-d127002-...",
          "category": "Attraction",
          "rating": { "value": 4.4, "max": 5 },
          "reviews_count": 7133
        }
      }
    ]
  }
}

Search returns places with ratings and review counts; the reviews endpoint then pulls traveler reviews with photos, owner replies, and translation info, each for 1 credit. A place with no matching reviews returns a 404 and refunds the credit. The place object matches every other SocialCrawl platform, so one parser handles TripAdvisor and everything else.

How the TripAdvisor APIs compare

ProviderCoverageSignup approvalUnified schemaPricing modelCheapest at volume
SocialCrawlSearch + reviewsNonePer credit (1 cr)n/a
TripAdvisor TerraOfficial contentSelf-servePay-as-you-goRate at signup
DataForSEOReviewsNonePer call / 10 results~$0.075/1,000
ApifySearch + reviewsNonePer result / actorfrom $0.50/1,000 reviews
Bright DataScraper + datasetNonePer record$1.30/1,000 at tier
SerpApiSearch + reviewsNonePer search$49/mo (5,000)

The TripAdvisor data APIs, ranked

1. SocialCrawl: unified public reviews and places, no approval

Best for: developers who want TripAdvisor search and reviews in a unified schema without a signup queue or attribution contract.

SocialCrawl covers the core TripAdvisor needs: search returns places with ratings and review counts, and reviews pulls traveler reviews with photos, owner replies, and translation info. Each request costs 1 credit, new accounts get 100 free credits, credits never expire, and a place with no matching reviews returns a 404 with the credit refunded. There is no partner approval and no display-attribution contract to sign, though you remain responsible for how you use the data.

The advantage is the unified schema: a TripAdvisor place and review match your social, commerce, and app data, so there is no one-off parser.

What we like:

  • Search plus reviews with photos, owner replies, and translation info
  • No approval queue, 1 credit per call, empty lookups refunded
  • Unified schema across 44 platforms
  • 100 free credits that never expire
  • Visual Explorer to preview before coding

What to watch:

  • Focused on search and reviews rather than the full official content catalog
  • Pricing is in GBP

Pricing: Free (100 credits, never expire), then Starter £15 (2,500 credits), Growth £49 (20,000 credits), Pro £299 (150,000 credits), Enterprise.

Verdict: The strongest pick for public TripAdvisor reviews and places without the official API's overhead.

2. TripAdvisor Terra API: the official successor

Best for: teams that need first-party, licensed TripAdvisor content and can meet display requirements.

Terra is TripAdvisor's replacement for the sunsetting Content API, and the headline change is that it is self-serve: no sales call and no approval queue for the standard tier. The first 1,000 calls are free, then it moves to pay-as-you-go (the per-call rate is shown after signup rather than published publicly). Display carries requirements: a bubble rating, the review date, and a TripAdvisor credit. The separate Hotel Pricing API is still contact-sales.

What we like: Official and licensed, now self-serve, free first 1,000 calls, canonical data source.

What to watch: Per-call rate only visible after signup, mandatory display attribution, Hotel Pricing still gated, own schema.

Pricing: First 1,000 calls free, then pay-as-you-go (rate shown at signup); Hotel Pricing API contact sales.

Verdict: The right choice when you need licensed first-party content and can meet the attribution rules. Note the legacy Content API sunset dates if you are migrating.

3. DataForSEO: cheapest per review at scale

Best for: high-volume review pulls where per-unit cost is the priority.

DataForSEO's Business Data TripAdvisor Reviews endpoint is the cheapest per review here: $0.00075 per call billed per 10 results, which works out to roughly $0.075 per 1,000 reviews. It is pay-as-you-go with a $50 minimum top-up. There is no unified schema and no approval, just very low unit cost.

What we like: By far the lowest per-review cost, pay-as-you-go, no approval.

What to watch: $50 minimum top-up, own schema, review-focused rather than a full toolkit.

Pricing: ~$0.075 per 1,000 reviews ($0.00075 per call, per 10 results), $50 minimum top-up.

Verdict: Unbeatable on unit cost for large review backfills if you can normalize the schema yourself.

4. Apify: custom TripAdvisor scrapers

Best for: teams that want a specific TripAdvisor scraper actor.

Apify's TripAdvisor actors start around $2.00 per 1,000 results, with dedicated reviews actors near $0.50 per 1,000 reviews, plus the platform's free monthly credits. Each actor is independently maintained with its own output shape.

What we like: Flexible marketplace, low per-review actors, free platform credits.

What to watch: No unified schema, per-actor variance, output shape depends on the actor.

Pricing: From $2.00 per 1,000 results; reviews actors from about $0.50 per 1,000 reviews; free platform credits.

Verdict: Good when a specific actor fits a niche a managed API does not.

5. Bright Data: enterprise per-record

Best for: enterprise teams pricing by record.

Bright Data offers a TripAdvisor scraper and a dataset variant: $1.50 per 1,000 records pay-as-you-go dropping to $1.30 per 1,000 at tier, the dataset variant from $2.50 per 1,000, and a free 5,000 page loads per month. Per-scraper output, no unified schema.

What we like: Enterprise reliability, generous free tier, dataset option.

What to watch: No unified schema, per-record economics, more infrastructure than API ergonomics.

Pricing: Free 5,000 page loads/mo, $1.50/1,000 records ($1.30 at tier), dataset from $2.50/1,000.

Verdict: Right for record-volume TripAdvisor workloads at enterprise scale.

6. SerpApi: for existing SerpApi users

Best for: teams already on SerpApi who want TripAdvisor in the same account.

SerpApi ships TripAdvisor Search and Reviews APIs from a shared search pool: 250 free searches per month, then a Developer plan at $49 per month for 5,000 searches. Results are real-time and billed on success.

What we like: Real-time, success-only billing, one account across many SERP types.

What to watch: Shared search pool, own schema, per-search rather than per-review economics.

Pricing: Free 250 searches/mo, Developer $49/mo (5,000 searches).

Verdict: Convenient if SerpApi is already in your stack.

Which TripAdvisor API fits which workflow?

  • Public reviews and places in one schema, no queue points to SocialCrawl
  • Licensed first-party content with attribution points to the official Terra API
  • Cheapest per review at scale points to DataForSEO
  • A specific custom scraper points to Apify
  • Enterprise per-record volume points to Bright Data
  • Already using SerpApi points to its TripAdvisor APIs

If you are migrating off the legacy Content API, decide first whether you need licensed first-party content (Terra) or public data in a unified schema (SocialCrawl). Paste a location into the Explorer to see the response shape.

What happened to the TripAdvisor Content API?

The legacy Content API is being retired: it sunsets on August 31, 2026, and the Partner API and Data Feeds follow on October 30, 2026. TripAdvisor's successor is the Terra API, which is self-serve rather than partner-gated, gives the first 1,000 calls free, and then bills pay-as-you-go with display attribution requirements (bubble rating, review date, and a TripAdvisor credit). If you built on the Content API, plan a migration before the sunset date. If you only need public reviews and places without an attribution contract, a third-party API like SocialCrawl is the simpler route.

Frequently asked questions

Is the TripAdvisor Content API still available?

Not for long. TripAdvisor's legacy Content API sunsets on August 31, 2026, with the Partner API and Data Feeds retiring on October 30, 2026. The replacement is the self-serve Terra API. If you built on the Content API, migrate before the sunset. For public reviews and places without a contract, SocialCrawl is an alternative that needs no approval.

What is the best TripAdvisor data API in 2026?

SocialCrawl leads for public reviews and places in a unified schema with no approval queue, at 1 credit per call. The official Terra API is the choice for licensed first-party content and can meet display attribution rules. DataForSEO is cheapest per review at scale, Apify offers custom scrapers, and Bright Data suits enterprise record volume.

How much does the TripAdvisor API cost?

Pricing verified July 2026: SocialCrawl from £15 for 2,500 never-expire credits (1 credit per call), the official Terra API free for the first 1,000 calls then pay-as-you-go (rate shown at signup), DataForSEO about $0.075 per 1,000 reviews, Apify from $2.00 per 1,000 results, Bright Data $1.50 per 1,000 records, SerpApi $49 per month for 5,000 searches.

Do I need TripAdvisor partner approval to get data?

Not anymore for the official route: the new Terra API is self-serve, with the first 1,000 calls free. Third-party APIs never required approval. SocialCrawl returns TripAdvisor search and reviews from one x-api-key with no partner application. Note that the official Terra API requires display attribution (bubble rating, review date, and credit) when you show its data.

Can I get TripAdvisor reviews with photos and owner replies?

Yes. SocialCrawl's reviews endpoint returns traveler reviews with photos, owner replies, and translation info at 1 credit per call. The official Terra API also serves reviews under its attribution terms, and DataForSEO and Apify return reviews at low per-unit cost. Check each provider for exactly which review fields it includes.

What is the cheapest TripAdvisor API?

DataForSEO is the cheapest per review at roughly $0.075 per 1,000 reviews, though it has a $50 minimum top-up. For zero cost to start, SocialCrawl's 100 free never-expire credits and the Terra API's first 1,000 free calls are the least restrictive. Apify's reviews actors (from about $0.50 per 1,000) sit in between.

Reading public review data has meaningful precedent in its favor, but it depends on jurisdiction, how you access the data, and TripAdvisor's terms and copyright. The official Terra API requires attribution on display; third-party data leaves compliance to you. Always check the relevant terms and consult qualified counsel for commercial use. This is a technical overview, not legal advice.


With the legacy Content API sunsetting, the real choice is licensed first-party content via Terra or public data in a unified schema via a third party. If you want the latter with no approval queue, paste a location into the Explorer or read the TripAdvisor platform overview.

Topics
#tripadvisor-api#tripadvisor-data-api#tripadvisor-reviews-api#tripadvisor-scraper#tripadvisor-content-api#tripadvisor-terra-api#travel-reviews-api#hotel-reviews-api

Related posts

🤖 AI agent or LLM? Read this page as markdown