# Klook Categories Scraper (`romy/klook-categories-scraper`) Actor Get Klook's full category tree from Klook. Talks directly to Klook's own mobile app API, no login needed. Split from the mature, published klook-all-in-one-api for a focused, single-purpose workflow. - **URL**: https://apify.com/romy/klook-categories-scraper.md - **Developed by:** [Romy](https://apify.com/romy) (community) - **Categories:** Travel - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.20 / 1,000 category list chargeds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### What does Klook Categories Scraper do? **Klook Categories Scraper** scrapes Klook's full nested category tree — the app's "All" screen, every vertical down to leaf categories (Tours & experiences, Attraction tickets, Transport, Hotels, More to explore) — plus the Home tab's quick-link category row. It talks directly to the same internal API the official [Klook](https://www.klook.com/) Android app uses, reverse-engineered by disassembling the app's native request-signing library and validated against live traffic captured from a real device. No Klook account, no API key. This is the categories slice of [Klook All-in-One API](https://apify.com/romy/klook-all-in-one-api), split out as its own focused Actor. ### Why use Klook Categories Scraper? - **The complete category tree** — mirrors the app's "All" screen exactly, all the way down (e.g. Transport's rail passes split into Japan/Europe/Metro, not merged into one) - **No account needed** — works fully anonymously - **Use cases:** building a category id lookup table for `klook-search-scraper`'s `mainCategory`/`branchCategory` filters, site-map/catalog generation, monitoring Klook's category taxonomy for changes ### How it connects to the parent This Actor is a narrow, batch-run spin-off of [klook-all-in-one-api](https://apify.com/romy/klook-all-in-one-api) (an always-on Standby REST API exposing every Klook endpoint). It reuses the parent's exact, proven request-signing logic (`klook-client.ts`, copied verbatim) but only wraps `/categories/tree` and `/categories`, and runs as a normal input-in/dataset-out Actor instead of a Standby API. ### Input | Field | Type | Description | | ------------------- | ------- | -------------------------------------------------------- | | `includeTree` | boolean | Fetch the full nested category tree. Default `true` | | `includeCategories` | boolean | Fetch the Home-tab quick-link categories. Default `true` | At least one of the two must be `true`. Example: `{}` (defaults: both fetched). ### Output One row per endpoint fetched. Real example (from the parent Actor's own live-confirmed capture of `GET /categories/tree`, trimmed to two sections): ```json { "type": "tree", "data": { "success": true, "tree": { "result": { "category": { "menus": [ { "title": "Things to do", "sub_menu_list": [ { "title": "Tours & experiences", "sub_menu_list": [{ "title": "Tours", "business_name": "9_Tours" }] } ] }, { "title": "Transport", "sub_menu_list": [{ "title": "Japan rail passes", "business_name": "35_Japan trains" }] } ] } } } } } ``` ### Known limitations - **Requires Apify's RESIDENTIAL proxy group.** Klook's edge blocks non-residential IPs with a DataDome bot-challenge page — confirmed directly from this development sandbox (a request byte-for-byte identical to a working one, sent without the proxy, came back as a DataDome JS-challenge HTML page, not JSON). All outbound requests route through `Actor.createProxyConfiguration({ groups: ['RESIDENTIAL'] })`. - **Local dev smoke testing outside the Apify platform needs "Proxy external access" enabled on the account.** This Actor's code was verified to be a byte-for-byte match against the parent's already-published, working `klook-client.ts`, and the local smoke test run during development failed exactly at the proxy-URL-acquisition step (`ProxyConfiguration: The "Proxy external access" feature isn't enabled for your account`) — before any request to Klook was even attempted. That's an account-tier restriction on pulling a proxy URL from *outside* a real platform Actor run, not a defect in this code; once deployed and actually run on Apify's platform, proxy access works through the normal SDK path. - **`categoryTree()` only works with an empty query string** — the app's own captured query params (app\_version, is\_hit\_navi, platform, ...) get rejected; the default (no-param) response is identical to what the app itself gets either way, so this isn't a limitation in practice. - **Leaf categories under the tree browse through the app's own internal search**, carrying the same category ids exposed by `klook-search-scraper`'s filters — no separate landing page per category. - This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Klook Travel Technology Limited. ### Pricing Pay per event. Charged **$0.002 per `category-list`** (FREE tier) — one event per row pushed to the dataset. See the Actor's Pricing tab for rates across all tiers. # Actor input Schema ## `includeTree` (type: `boolean`): Fetch the full nested category tree (GET /categories/tree). ## `includeCategories` (type: `boolean`): Fetch the Home-tab quick-link categories (GET /categories). ## Actor input object example ```json { "includeTree": true, "includeCategories": true } ``` # Actor output Schema ## `dataset` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("romy/klook-categories-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("romy/klook-categories-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call romy/klook-categories-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/klook-categories-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/SgQZML1yu2Mg4V4Fo/builds/WlbkhLSJPs39Y5bTh/openapi.json