KKday Activities Scraper

Scrape KKday travel activities, tours and experiences by keyword or pasted URL. Every record carries the selling price range, the original price, the discount, ratings, booking demand, destinations and images. Flip one toggle to add the full description, meeting address, coordinates and price tiers.

What it collects

Search mode reads KKday keyword result pages (/product/productlist), newest first, 10 per page, paging forward until Max items or the end of results. URL mode reads pasted activity pages (/product/<id>) or continues a pasted search page forward. Detail enrichment opens each activity page for the long description, address, latitude and longitude, and the full price tier list.

Sample output (illustrative placeholders, not live listings):

Activity	From	Rating	Booked
Sample Harbor Sunset Cruise	USD 24.50	4.7 (1,204)	8K+ booked
Sample Old Town Walking Tour	USD 12.00	4.8 (3,410)	21K+ booked

• Emit unchanged and Emit expired return, and bill, extra rows (billed as dataset items); leave them off unless you want full snapshots or expiry tracking. Emit expired rows are produced only when a run fully scans the tracked scope, never when Max items capped the run or a pasted URL could not be read.

Send results into your apps (MCP connectors)

Results can be piped into the apps you already use through Model Context Protocol (MCP) connectors, as an optional side channel. This never changes the dataset output.

• mcpConnectors: authorize a connector under Apify, Settings, API & Integrations, then select it here. Notion receives a page per record; other connectors receive a best-effort write or digest. Each connector gets a condensed summary per record; the complete record always stays in the dataset.
• notionParentPageUrl: the Notion page under which record pages are created. Required for the Notion connector, ignored by the others.
• maxNotifyListings: cap on records written to each connector per run.

Connection

KKday's edge refuses datacenter exits, so residential proxy exits are preselected (Singapore default; switch the country to your market). No account is needed; only public catalog pages are read.

Resume and recurring updates

• Resume from run or dataset: skips activity IDs already saved by a previous run.
• Incremental monitoring: tracks the same search across scheduled runs and returns only NEW, UPDATED or REAPPEARED rows, with changedFields naming what moved. Combine with Emit unchanged or Emit expired to also return those rows (each returned row is billed).
• Incremental monitoring cannot be combined with Resume from run when a baseline already exists for the same state key.

Pricing

Pay per event: Actor start, one Activity record per saved row (primary), plus Activity details once per record only when detail enrichment actually enriched and saved that row.