Klook Activities & Experiences Scraper

Extract Klook activities and experiences at scale — search by keyword or browse an entire city's catalog. Built on Klook's mobile API (not fragile HTML scraping), so it returns clean, structured data reliably and fast.

Who it's for

• Travel & OTA analysts — benchmark activity prices, ratings and popularity across destinations and competitors.
• Affiliates & content sites — build "things to do in <city>" pages with live prices, ratings and images.
• Market researchers — track demand (bookings, reviews) for tours, attractions and experiences by city or theme.
• PropTech / travel-tech developers — a stable JSON feed of Klook inventory for apps, dashboards and price-comparison tools.

What you get (output fields)

Field	Type	Description
activity_id	integer	Klook activity ID
title	string	Activity/experience name
activity_url	string	Canonical Klook activity page URL
rating	float	Average review score (0–5)
review_count	integer	Number of reviews
booked_count	integer	Total bookings ("participants")
currency	string	Currency of the prices
sell_price	float	Current selling price (lead)
market_price	float	Original / list price
price_from / price_to	float	Price range across packages
sold_out	boolean	Whether the activity is sold out
city_id / city_name	int / string	City
country_id / country_name	int / string	Country
latitude / longitude	float	GPS coordinates
image_url	string	Cover image URL
template_id / leaf_category	integer	Klook product/category codes
earliest_start_time	string	Earliest available start time
source_query / source_city_id	string / int	What produced this row
scraped_at	string	ISO-8601 timestamp

High-value use cases

1. Price intelligence — pull the same attractions across cities/currencies and monitor sell_price / price_from over time.
2. Destination pages — generate ranked "top activities in Tokyo/Osaka/Bangkok" lists with ratings, reviews and images.
3. Demand research — rank experiences by booked_count and review_count to spot trending tours and attractions.
4. Competitive benchmarking — compare Klook inventory and pricing against other OTAs for the same destinations.

Input parameters

Field	Type	Default	Notes
searchQueries	array	—	Keywords to search (e.g. "universal studios japan").
cityIds	array	—	Klook city IDs to browse (e.g. 28 = Tokyo, 29 = Osaka).
sortBy	string	default	default, most_reviewed, price_low_high, price_high_low, rating.
maxItems	integer	100	Total activities to collect. 0 = no limit.
currency	string	USD	ISO currency code for prices.
language	string	en_US	Content locale.
proxyConfiguration	object	off	Optional proxy (residential improves anti-bot reliability).

Provide searchQueries, cityIds, or both — at least one is required.

Example input

{
    "searchQueries": ["universal studios japan"],
    "cityIds": ["28"],
    "sortBy": "most_reviewed",
    "maxItems": 100,
    "currency": "USD",
    "language": "en_US"
}

Example output row

{
    "activity_id": 46604,
    "title": "Universal Studios Japan Studio Pass",
    "activity_url": "https://www.klook.com/activity/46604/",
    "rating": 4.8,
    "review_count": 87652,
    "booked_count": 6158371,
    "currency": "USD",
    "sell_price": 38.2,
    "price_from": 38.2,
    "price_to": 51.1,
    "city_name": "Osaka",
    "country_name": "Japan",
    "latitude": 34.6656768,
    "longitude": 135.4323185,
    "image_url": "https://res.klook.com/image/upload/activities/dgsxci9mi5z0rhnozwtm.jpg/w576h384c85/plus/webp",
    "scraped_at": "2026-07-13T07:26:35Z"
}

Finding city IDs

Use the companion Klook MCP Server actor's search_suggestions tool, or run this actor with a searchQueries value first — each result carries city_id and city_name you can reuse in cityIds.

Scheduling & integrations

Schedule runs (daily/weekly) from the Apify Console and pipe results to Google Sheets, Make, Zapier, S3 or your own API via Apify webhooks and the dataset API (JSON, CSV, Excel).

MCP / AI assistants

Prefer live, on-demand access from Claude, Cursor, ChatGPT or your own agents? Use the companion Klook MCP Server actor, which exposes activity search, city browsing, suggestions and category tools over the Model Context Protocol.

FAQ

Where does the data come from? Klook's official mobile backend API — the same source the Klook app uses — which is why it's more reliable than HTML scraping.

How fresh is the data? Live at run time. Prices, ratings and bookings reflect Klook at the moment of the request.

Are reviews included? This actor returns each activity's aggregate rating and review_count. Individual review text is out of scope.

Do I need a proxy? Usually no. If the anti-bot handshake is challenged from a datacenter IP, enable a residential proxy in proxyConfiguration.

Is scraping legal? You are responsible for how you use the data. This tool collects publicly available catalog information; respect Klook's terms and applicable laws.