TripAdvisor Search Scraper

What does TripAdvisor Search Scraper do?

TripAdvisor Search Scraper takes one or more free-text destination queries (e.g. "Bangkok") and pushes real destination/POI autocomplete results — the same suggestions, with the same numeric geo_id values, that the TripAdvisor app itself returns as you type. Optionally also fetches the TripAdvisor home tab feed once per run.

It talks directly to the same internal API the official TripAdvisor Android app uses, reverse-engineered by capturing live traffic from a real device. Unlike many reverse-engineered mobile APIs, TripAdvisor needs no per-request signature at all — just a static API key and self-generated device/session ids, confirmed live and standalone-reproducible. No TripAdvisor account, no API key of your own needed. This is the search/home slice of TripAdvisor All-in-One API, split out as its own focused batch Actor.

Why use TripAdvisor Search Scraper?

• Real destination ids, not guesses — every result carries a numeric geo_id that plugs straight into TripAdvisor's hotel/restaurant/attraction search
• Batch multiple queries in one run — pass an array of destination names, get one dataset row per query
• Optional home feed — grab TripAdvisor's home tab content once per run alongside your searches
• No account needed — every call works fully anonymously
• Use cases: destination lookup for a downstream hotel/restaurant/attraction pipeline, travel content aggregation, autocomplete testing, geo-id discovery

How it connects to the parent

This Actor wraps exactly two of the parent TripAdvisor All-in-One API's Standby REST endpoints — GET /search and GET /home — as a standalone batch-run Actor: give it an input JSON with a list of queries, get dataset rows out. No always-on Standby container, no per-call billing loop — just run it, get your rows, done. If you need hotel/restaurant/attraction search, detail pages, reviews, or photo galleries, use the parent Actor directly (or another spin-off) with the geo_id values this Actor returns.

Input

Field	Type	Description
queries	string[]	Required. Free-text destination names to search, e.g. "Bangkok".
currency	string	ISO currency code, affects prices in results. Default "GBP".
includeHome	boolean	Also fetch the TripAdvisor home tab feed once and push it as an extra dataset row. Default false.

Example:

{
    "queries": ["Bangkok", "Paris"],
    "currency": "USD",
    "includeHome": true
}

Output

One dataset row per query:

{
    "query": "Bangkok",
    "results": { "...": "AppPresentation_TypeaheadV2 response, including numeric geo_id values" }
}

Plus, if includeHome is true, one extra row after the query rows:

{
    "home": { "...": "HomeData response" }
}

Data notes

• No request signing exists at all — confirmed by capturing the real app's traffic and finding just static identity headers (no per-request signature or hash) that aren't validated against any server-side registry (confirmed: a freshly generated device identity works immediately). Verified fully standalone-reproducible — no device or live app session needed at runtime.
• One internal API endpoint, persisted queries. Every request goes to a single internal endpoint, distinguished by an operation name plus a fixed persisted-query hash instead of a full query string — confirmed live that these hashes are reusable across devices/sessions.
• currency changes real prices, not just a symbol. Not part of any request signature (there isn't one here), so any ISO code is always safe to pass.

Known limitations

• Search only, no downstream lookups. This Actor returns destination/POI suggestions and the home feed; it does not fetch hotels, restaurants, attractions, detail pages, reviews, or photos — use the parent TripAdvisor All-in-One API or another spin-off Actor for those, feeding in the geo_id values this Actor returns.
• This Actor only wraps guest-accessible endpoints. No login flow is implemented or planned.
• This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Tripadvisor LLC. Behavior may change if TripAdvisor changes its API.

Pricing

Pay per event: $0.002 per search-result — charged once for each destination-search row and once for the optional home-feed row pushed to the dataset (Free plan price; lower on paid Apify plans). See the Actor's Pricing tab for current tiered rates.

Found a bug or have a feature request? Use the Issues tab on this Actor's page.