Skip to content
ScoutingAPI

The TripAdvisor data API without the gatekeeping.

TripAdvisor’s official Content API is gated — key approval, usage caps, and attribution rules. ScoutingAPI gives you the same unified schema, self-serve: live cross-OTA hotel prices and reviews across Airbnb, Booking, Vrbo & Google today, with TripAdvisor coverage on the roadmap on the very same contract.

100 credits free · no card · start on the Core-4 now, we’ll email you when TripAdvisor is live

99.9% uptime SLAFailed calls cost 0 creditsNative MCP for AI agentsOne unified schema
Response · /v1/search
Request
GET /v1/search
  ?location=Sibenik, HR
  &checkIn=2026-07-13&checkOut=2026-07-20
  &adults=2&children=2
  &platforms=airbnb,booking,vrbo,google
Response
{
  "data": [
    {
      "id": "stays_booking_abramovic2",
      "platform": "booking",
      "name": "Apartments Abramovic 2",
      "propertyType": "apartment",
      "location": { "city": "Sibenik", "region": "Sibenik-Knin", "country": "HR" },
      "starRating": 4, "guestRating": 9.4, "ratingScale": 10, "reviewCount": 318,
      "amenities": ["kitchen", "wifi", "air_conditioning", "sea_view"],
      "price": { "currency": "EUR", "nightlyPrice": 303, "totalPrice": 2122, "nights": 7 }
    },
    {
      "id": "stays_airbnb_42307961",
      "platform": "airbnb",
      "name": "Seafront villa near Sibenik with pool",
      "propertyType": "villa",
      "location": { "city": "Sibenik", "region": "Sibenik-Knin", "country": "HR" },
      "starRating": null, "guestRating": 4.92, "ratingScale": 5, "reviewCount": 86,
      "amenities": ["pool", "kitchen", "wifi", "sea_view"],
      "price": { "currency": "EUR", "nightlyPrice": 375, "totalPrice": 2625, "nights": 7 }
    }
  ],
  "meta": {
    "platforms": ["airbnb", "booking", "vrbo", "google"], "cached": false,
    "creditsCharged": 20, "currency": "EUR",
    "platformResults": [
      { "platform": "airbnb",  "status": "ok", "count": 1 },
      { "platform": "booking", "status": "ok", "count": 1 },
      { "platform": "vrbo",    "status": "ok", "count": 1 },
      { "platform": "google",  "status": "ok", "count": 1 }
    ],
    "pagination": { "cursor": null, "hasMore": true }
  }
}

The schema TripAdvisor will return — already live across four platforms.

This is an actual multi-platform /v1/search response. TripAdvisor is on the roadmap on this exact contract; when it lands it returns the same object shape you see here today for Airbnb, Booking, Vrbo, and Google.

Same schema acrossAirbnbBooking.comVrboGoogle Hotels
id + platform

Stable composite id and the source platform — identical keys for every platform, TripAdvisor included when it lands.

guestRating + ratingScale

Rating with its native scale (Airbnb 5, Booking 10) so scores stay comparable — TripAdvisor’s 5-point rating fits the same field.

reviewCount

Review volume per property; full normalized reviews come back via /v1/reviews today for the Core-4.

amenities[]

One canonical taxonomy — pool, wifi, sea_view — across every platform.

price

Live nightly + total with a fee breakdown when you pass dates; cross-OTA min/median via /v1/price-compare.

meta.platformResults

Per-platform status and count; a new platform is just one more entry here — no schema change.

Honest scope: TripAdvisor is fast-follow, not live in v1. Everything above is real, returned today across the Core-4 — and reviews already come back normalized via /v1/reviews. When TripAdvisor coverage ships, it slots into platforms[] with no change to your code.

Instant access. No key-approval queue. No attribution rules.

TripAdvisor’s Content API requires key approval, enforces usage caps and attribution rules, and is reviews/location-focused. ScoutingAPI is self-serve: sign up, get a key, and start on the live Core-4 in under five minutes — with TripAdvisor coverage arriving on the same key.

100 free credits — no credit card

Build and test against real responses across the live Core-4 before you decide anything.

scout_test_ sandbox at zero cost

Deterministic fixtures wire up your integration before you ever spend a credit.

One schema, no rework later

Build against the unified schema now; TripAdvisor slots in on the same contract — no migration when it ships.

  1. 1Get your free key
  2. 2curl the /v1/search example
  3. 3Join the TripAdvisor waitlist

Reliability you can build a product on.

Scrapers and RapidAPI listings give you raw data and a shrug. We run a product — monitoring, multi-source failover, retries, and caching behind one contract.

99.9% monthly uptime SLA

Committed on the ScoutingAPI response envelope and published on a public status page. Multi-source failover, retries, and caching sit behind one contract.

Failed calls cost 0 credits

Failed, empty, or blocked calls are never charged. If a source is briefly unreachable you get a typed upstream_unavailable and we charge nothing — not the pay-per-attempt model of raw scrapers.

Honest coverage, surfaced in meta

We don’t claim platforms we haven’t shipped. Live platforms return data; roadmap platforms aren’t advertised as live. meta.platformResults tells you exactly what answered, every call.

99.9%Monthly uptime SLAOn the ScoutingAPI envelope, backed by a public status page.
0 creditsFor failed or bad dataEmpty, blocked, or upstream-degraded calls are never charged.
Core-4 liveTripAdvisor on the roadmapAirbnb, Booking, Vrbo & Google today — TripAdvisor on the same contract.
1 schemaEvery platform, every endpointWrite your code once; a new platform is just one more entry.

curl it, import the SDK, or hand it to your agent.

Every sample is copy-paste runnable against your free key and generated from @scoutingapi/sdk, so it never drifts from the live API. TripAdvisor joins the same platforms list when it ships.

curl -s -G "https://api.scoutingapi.com/v1/search" \
  -H "Authorization: Bearer scout_test_YOUR_KEY" \
  --data-urlencode "location=Sibenik, HR" \
  --data-urlencode "checkIn=2026-07-13" \
  --data-urlencode "checkOut=2026-07-20" \
  --data-urlencode "adults=2" \
  --data-urlencode "children=2" \
  --data-urlencode "platforms=airbnb,booking,vrbo,google" \
  --data-urlencode "limit=20"
# Core-4 is live today; TripAdvisor joins this same call on the roadmap.

Reviews already come back normalized today: call /v1/reviews for the Core-4. The MCP tab adds ScoutingAPI’s native server (Streamable HTTP, OAuth 2.1 / PKCE) to Claude, Cursor, or n8n, with read-only tools for search, reviews, price, and price-compare.

TripAdvisor data: official Content API, raw scraper, reviews tool, or ScoutingAPI?

CapabilityScoutingAPIOfficial TripAdvisor Content APIRaw scraper / RapidAPISTR analytics (AirROI / AirDNA)
AccessSelf-serve, free key in minutesKey approval + usage caps + attribution rulesSelf-serve, but per-actor$10 min (AirROI) / ~$50k, sales-gated (AirDNA)
TripAdvisor coverageRoadmap — same schema; Core-4 live todayTripAdvisor content onlyPer-actor, inconsistentNone
Platform coverageAirbnb + Booking + Vrbo + Google (hotels and STR)TripAdvisor onlyOne platform per actorAirbnb / Vrbo only (STR)
Reviews + price togetherYes — normalized reviews and live price in one schemaReviews / location focus; limited live pricingWhatever the actor returnsAnalytics, not live reviews/price
Cross-OTA price-compareYes — one property, every OTA, computed min / medianNoNoNo
Output schemaOne unified schema, every platformTripAdvisor-specificDifferent shape per actorAnalytics-specific
Reliability99.9% SLA, status page, failoverPlatform-dependentNone (no SLA)Vendor-dependent
Failed-call billingFree — 0 creditsn/aYou pay per attemptn/a
Agent-native (MCP)First-class MCP + OAuth + ConnectorsNoBolt-on per actorNo

The honest read: TripAdvisor’s Content API gates you and covers TripAdvisor only; scrapers give you a per-actor shape with no SLA; analytics tools answer a different question. ScoutingAPI is the unified, self-serve, agent-native API — Core-4 live today, TripAdvisor on the roadmap on the same schema, so you build once and gain coverage without rework.

What developers and agents build on the unified reviews + price API.

TripAdvisor is on the way — but the schema, reviews, and cross-OTA price are live today across the Core-4, so you can start now.

Cross-platform review intelligence

Pull normalized reviews and ratings across Airbnb, Booking, and Vrbo via /v1/reviews — one schema, ready for sentiment analysis — with TripAdvisor reviews joining the same feed when it lands.

Reputation monitoring

Track a property’s rating and review volume across platforms over time; alert on a new low review or a rating dip — without a different integration per site.

Cross-OTA rate shopping

Run /v1/price-compare for a hotel and get every OTA’s rate with computed min / median — the price half of the “reviews + price” decision travelers actually make.

Travel-planning & sourcing agents

Give your AI agent reviews, ratings, and live price in one normalized tool via the native MCP server — so it recommends well-reviewed stays at the best rate.

Market-rate & sentiment intelligence

Combine cross-platform ratings with live cross-OTA price across a market and date range to map both quality and value — not last quarter’s analytics.

Build once, gain TripAdvisor for free

Integrate the unified schema now against the live Core-4; when TripAdvisor coverage ships it slots into platforms[] with zero code change — no migration, no rework.

TripAdvisor API — frequently asked questions

The questions developers actually search — answered in full and honestly, with FAQ structured data for rich results.

Get your free key — and join the TripAdvisor waitlist.

100 credits, no credit card. Build on the live Core-4 today; we’ll email you when TripAdvisor ships.

No credit card · failed calls cost 0 credits · TripAdvisor on the roadmap, same schema