# Klook Home Feed Scraper (`romy/klook-home-feed-scraper`) Actor

Get Klook's Home tab content feed 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-home-feed-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 feed item 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 Home Feed Scraper do?

**Klook Home Feed Scraper** scrapes Klook's Home tab live content feed and discovery rails: the paginated Recommended/Nearby/seasonal feed, the richer "Nearby gems" widget (and its full "see more" list), "Where to next?" destination suggestions, the "Recently viewed" rail, and the Trips tab's inspiration carousel.

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 Home-tab 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 Home Feed Scraper?

- **The whole Home tab in one Actor** — Recommended, Nearby (location-based), whatever seasonal rail Klook is currently running, "Nearby gems", "Where to next?", "Recently viewed", and the Trips tab's inspiration carousel
- **Real, working pagination** on the main feed — confirmed live by the parent Actor with real result counts
- **No account needed** — every endpoint works fully anonymously
- **Use cases:** travel content aggregation, home-feed monitoring, destination-suggestion mining, recently-viewed tracking for a session pipeline

### 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 the Home-tab endpoints — `/home/feed/tabs`, `/home/feed`, `/home/nearby`, `/home/nearby/more`, `/home/where-to-next`, `/recently-viewed`, `/trips/inspiration` — and runs as a normal input-in/dataset-out Actor instead of a Standby API.

### Input

| Field                 | Type    | Description                                                                                                    |
| ---------------------- | ------- | ---------------------------------------------------------------------------------------------------------------- |
| `section`               | string  | Which widget to fetch: `feed` (default), `feedTabs`, `nearby`, `nearbyMore`, `whereToNext`, `recentlyViewed`, `tripInspiration` |
| `tab`                   | string  | A tab value from `feedTabs`, e.g. `1`=Recommended, `6`=Nearby. Used when `section=feed`. Default `"1"`             |
| `page`                  | integer | Start page for `section=feed`. Default `1`                                                                        |
| `size`                  | integer | Results per page for `section=feed`. Default `10`                                                                 |
| `maxPages`              | integer | Stop after this many pages (`section=feed`). Default `10`                                                         |
| `maxItems`              | integer | Stop once this many items have been pushed (`section=feed` only)                                                   |
| `lat` / `lng`           | number  | Required for `nearby`/`nearbyMore`. Optional for `feed` (Nearby tab) and `whereToNext`                              |
| `limit`                 | integer | Cards to return for `nearby`, `whereToNext`, `recentlyViewed`                                                       |
| `currency`              | string  | ISO code, affects prices in `recentlyViewed`                                                                       |

Example:

```json
{ "section": "nearby", "lat": -6.2884, "lng": 106.7183, "limit": 5 }
```

### Output

One row per item for `section=feed`/`nearbyMore` when the response is a list, otherwise one row wrapping the raw response. Real example (from the parent Actor's own live-confirmed capture of `GET /home/nearby?lat=-6.2884&lng=106.7183&limit=1`):

```json
{
    "section": "nearby",
    "data": {
        "success": true,
        "nearby": {
            "result": {
                "title": "Nearby gems in South Tangerang",
                "recommend_cards": [{ "data": { "title": "Up at Thamrin Nine Observatory Deck in Jakarta" } }]
            }
        }
    }
}
```

### 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.
- **Home feed cards were audited by the parent Actor for non-activity content and found to be activities only.**
- **`/home/where-to-next`'s "See more" opens a plain klook.com webpage, not an API call.**
- This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Klook Travel Technology Limited.

### Pricing

Pay per event. Charged **$0.0015 per `feed-item`** (FREE tier) — one event per row pushed to the dataset. See the Actor's Pricing tab for rates across all tiers.

# Actor input Schema

## `section` (type: `string`):

Which Home-tab widget to fetch.

## `tab` (type: `string`):

A tab value from section "feedTabs", e.g. 1=Recommended, 6=Nearby. Used when section=feed.

## `page` (type: `integer`):

1-indexed starting page for section=feed.

## `size` (type: `integer`):

Results per page for section=feed.

## `maxPages` (type: `integer`):

Stop after this many pages for section=feed.

## `maxItems` (type: `integer`):

Stop once this many items have been pushed (section=feed only).

## `lat` (type: `number`):

Required for location-dependent sections: nearby, nearbyMore. Optional for feed (Nearby tab) and whereToNext.

## `lng` (type: `number`):

See latitude.

## `limit` (type: `integer`):

Number of cards to return for section=nearby, whereToNext, or recentlyViewed.

## `currency` (type: `string`):

ISO currency code, affects prices in section=recentlyViewed.

## Actor input object example

```json
{
  "section": "feed",
  "tab": "1",
  "page": 1,
  "size": 10,
  "maxPages": 10
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/klook-home-feed-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("romy/klook-home-feed-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-home-feed-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/klook-home-feed-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/neLC8cwdku9ruKqQu/builds/eSxVgfu5lksCDmP3Z/openapi.json