# Klook Destination Guide Scraper (`romy/klook-destination-guide-scraper`) Actor

Get destination guides and trending sights 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-destination-guide-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.60 / 1,000 destination 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 Destination Guide Scraper do?

**Klook Destination Guide Scraper** takes one or more Klook destination (city) ids and pushes each city's full destination guide — share info, i18n city name, and every content tab (Highlights, Attractions & landmarks, Hotels, Deals, Food & dining, ...) — plus its trending points-of-interest list, one dataset row per destination id.

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 destination-guide 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 Destination Guide Scraper?

- **Two calls in one row** — the full city guide and its trending points of interest, fetched in parallel and merged into a single dataset item per destination id
- **A dedicated city-guide screen, not a search filter** — confirmed live by the parent Actor: tapping a city from Klook's Trending destinations rail fires this exact endpoint, distinct from `/search` with a city filter
- **Rich per-POI descriptions** — trending sights come with their own long-form description and tags, plus related bookable activities, not just a title/image
- **No account needed** — every read request works fully anonymously
- **Use cases:** destination-guide content aggregation, city landing-page generation, points-of-interest enrichment for a travel app

### 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 `/destinations/{id}` and `/destinations/{id}/trending-sights`, and runs as a normal input-in/dataset-out Actor instead of a Standby API.

### Input

| Field                   | Type     | Description                                                                                                  |
| ----------------------- | -------- | ------------------------------------------------------------------------------------------------------------ |
| `destinationIds`        | string\[] | **Required.** Klook destination/city ids (same id used elsewhere as `city_id`), e.g. `28`=Tokyo, `29`=Osaka. |
| `includeTrendingSights` | boolean  | Also fetch each destination's trending points-of-interest list. Default `true`                               |

Example:

```json
{ "destinationIds": ["28", "29"] }
```

### Output

One dataset row per destination id:

```json
{
    "destinationId": "28",
    "guide": { "...": "full destination guide (share info, i18n name, content tabs)" },
    "trendingSights": { "...": "trending points of interest, each with a description and tags" }
}
```

### 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.
- **No search/discovery of destination ids here** — use `klook-search-scraper` or `/search/init`'s trending destinations to find ids first.
- 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 `destination`** (FREE tier) — one event per destination id processed. See the Actor's Pricing tab for rates across all tiers.

# Actor input Schema

## `destinationIds` (type: `array`):

Klook destination/city ids (same id used elsewhere as city\_id), e.g. 28=Tokyo, 29=Osaka.

## `includeTrendingSights` (type: `boolean`):

Also fetch each destination's trending points-of-interest list.

## Actor input object example

```json
{
  "destinationIds": [
    "28"
  ],
  "includeTrendingSights": 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "destinationIds": [
        "28"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/klook-destination-guide-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "destinationIds": ["28"] }

# Run the Actor and wait for it to finish
run = client.actor("romy/klook-destination-guide-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 '{
  "destinationIds": [
    "28"
  ]
}' |
apify call romy/klook-destination-guide-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/klook-destination-guide-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 <APIFY_API_TOKEN>` 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/VoppLYc6VdmnEuXXS/builds/n16E14FrsW7YFKA3R/openapi.json