Klook Activity Price Tracker — Tours, Attractions & Tickets

Track prices for Klook activities — tours, attractions, theme-park tickets, day trips and experiences. Search any destination or activity keyword and get clean, structured records with the live selling price, market price, currency, rating, booked-count and active promotion tags. Built for OTA-affiliate marketers, travel-product teams and price/promotion monitoring.

What you get — one flat record per activity

Field	Description
activity_id, title	Klook activity id and title
category, city_name, sub_title	Activity category and destination
selling_price	Localized price string as shown (e.g. US$ 49)
price_amount, currency	Parsed numeric amount and currency symbol
market_price, market_price_amount	Strike-through / reference price when present
rating, review_count, booked	Star rating, review count, booked-count
sold_out	Availability flag
promotions	Active promotion / discount tag texts
cover_url, url	Cover image and direct Klook activity link

Why this one

• Activities, not hotels. Most travel scrapers cover accommodation; this one targets the tours-and-activities side that OTA affiliates actually monetize.
• Live prices straight from Klook's own data. Reads Klook's internal search service, so you get the full result set with real selling prices — not a thin slice of the rendered page.
• Built to be scheduled. Re-run on a destination or activity query to watch prices and promotions move; price_amount + currency are parsed for easy diffing.
• No key required. Runs through Apify residential proxy; no Klook account or API key needed.

Example input

{
  "query": "Tokyo",
  "currency": "USD",
  "language": "en_US",
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Pricing

Pay per result — you are charged for each activity returned. Run ad-hoc or schedule it; you only pay for the activities you collect.

Notes

Collects publicly available activity listing information for legitimate market-research and price-monitoring use. Klook may localize the displayed currency to the proxy region; the selling_price string always carries its own currency symbol and currency is parsed from it.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.