Ikyu.com Scraper — Japan Luxury Hotels & Ryokan Prices
Pricing
from $5.00 / 1,000 per records
Ikyu scraper for Japan luxury hotel prices: high-end hotels & ryokan with ratings and advertised prices from ikyu.com by prefecture and area — clean English schema for rate shopping. Unofficial; not affiliated with Ikyu Corporation / LY Corporation.
REQUIRED. Choose one of the 47 prefectures by its English name (e.g. "Tokyo", "Osaka", "Kyoto"). Via API/CLI pass the English name exactly as listed (e.g. "Tokyo", not "東京都" / "13" / "tokyo-to" — the platform validates the list before the run starts and rejects anything else with the list of valid values). Cities are NOT prefectures: use "Kanagawa" for Yokohama, "Aichi" for Nagoya, "Osaka" for Osaka-shi. ikyu.com area hubs are prefecture-scoped; narrow further with area / keyword / accommodationType.
Optional. Leave empty to search ALL areas of the prefecture (recommended for a first run). To narrow: an ikyu area code ("ma026005", from ikyu.com URLs) or a substring of the JAPANESE area name (e.g. "京都駅" matches 京都駅周辺; romaji such as "Gion" matches nothing). If the value matches none of the prefecture's areas the run stops after the hub page with the full list of valid areas. Do NOT put a prefecture name here.
Optional. Case-insensitive substring filter on the facility name (Japanese or English), applied client-side after fetching — a rare keyword may need a higher maxApiRequests to fill maxItems.
Optional, default all. Facility-type filter applied client-side on ikyu's published type: hotel (city/business/resort hotels), ryokan (traditional inns; "inn" / 旅館 also accepted via API) or villa (vacation rentals).
Optional, default false. When true, each facility costs one extra request but adds check-in/check-out times, an onsen flag and amenity flags (pool, gym, airport shuttle …). When false (default) the actor emits list data only — name, type, area, address, geo, rating, review count, room count, lowest advertised price — which is already rich on ikyu.com.
Optional, default 10. Stop after this many facility records (1..10000). Each list page yields up to 20 facilities; with includeDetails each record also needs one detail request, so raise maxApiRequests accordingly.
Optional, default 120. Hard budget of HTTP requests to ikyu.com for this run (1 hub page + list pages of 20 facilities + 1 per facility detail if enabled). Requests are strictly serial with >= 1.2 s spacing, so a 300-request run takes about 6 minutes of upstream time. Raise it when you ask for a large maxItems WITH includeDetails, since each facility detail costs one request. When the budget runs out the run still SUCCEEDS with the records collected so far and complete=false in RUN_SUMMARY (not an error).
Apify proxy settings. Required: ikyu.com blocks datacenter IP ranges (HTTP 403), so the default uses Apify RESIDENTIAL proxies (country JP). Proxy bandwidth is billed as Apify platform usage. Never used for rotation/evasion — one client identity per run.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "JP"}