Japan Luxury Hotels & Ryokan (ikyu.com)

Japan's curated luxury accommodation market — hotels, ryokan and villas from ikyu.com (一休.com), with ratings, room counts, geo coordinates and advertised prices, in a clean English schema.

This Actor searches ikyu.com's public area listings by prefecture and area and returns each facility as English-schema JSON: name, facility type (hotel/ryokan/villa), area and prefecture (with JIS code and English name), full address and postal code, latitude/longitude, guest rating and review count, total room count, and the lowest advertised price in JPY (tax included, for the site-default party of 2 adults / 1 night / 1 room). Optional detail fetches add check-in/check-out times, an onsen flag and amenity flags (pool, gym, airport shuttle …).

ikyu.com is Japan's invitation-based luxury OTA — facilities are curated, skewing to 4–5 star hotels, high-end ryokan and villas that often never list on international platforms. The site is Japanese-only, which makes this segment invisible to most international tooling. This Actor is the bridge.

Unofficial tool. Not affiliated with or endorsed by Ikyu Corporation or LY Corporation. It collects publicly available data only (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion, robots.txt-open pages only), and extracts factual business data only — no review texts, no reviewer names, no marketing prose, no phone numbers, no personal data of any kind (relevant e.g. under GDPR: no personal data is collected or processed). Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

---

Quick start — verified input

Copy-paste this into the Actor's input (JSON tab) or pass it via API — it was run successfully on 2026-09-02 (10 luxury hotels around Kyoto Station, list data, ~30 seconds; the default RESIDENTIAL JP proxy is applied automatically):

{
  "prefecture": "Kyoto",
  "area": "京都駅",
  "maxItems": 10
}

Common input mistakes

Wrong	Right	Why
"prefecture": "Kyoto-shi" / "Hakone" / "Karuizawa"	"prefecture": "Kyoto" / "Kanagawa" / "Nagano"	prefecture must be one of the 47 prefectures (English name, dropdown). Resorts and cities go in area (Japanese), or nowhere.
"prefecture": "京都府" or "26" (via API)	"prefecture": "Kyoto"	The platform checks the 47 English names before the run starts; other spellings are rejected with the valid list.
"area": "Gion"	"area": "祇園" (or the ma… code from an ikyu URL)	Areas are matched against Japanese names from the prefecture hub; romaji matches nothing (the run warns, then stops with the list of valid areas).
"area": "Kyoto"	leave area empty	area is a sub-area of the prefecture, not the prefecture itself.
"accommodationType": "Ryokan inn"	"accommodationType": "ryokan"	One of all / hotel / ryokan / villa (dropdown).
"proxyConfiguration": { "useApifyProxy": false }	keep the default (RESIDENTIAL, country JP)	ikyu.com answers HTTP 403 to datacenter IPs; the default residential proxy is required.

Every invalid value stops the run immediately (before any upstream request) with a message that names the field and lists the valid values. Fields with a fixed list of values are validated by the Apify platform before the run even starts.

Empty results?

A run that finishes with items: 0 and complete: true is not an error. Typical causes: a keyword that no facility name contains (client-side substring filter — try a shorter Japanese fragment such as リッツ → リッツ/Ritz), an accommodationType that does not exist in a small area (e.g. villa in a city-centre area), or a small maxApiRequests with a rare keyword. Widen the query and re-run.

---

Who is this for?

• Luxury travel agencies & concierge services — inventory awareness of Japan's high-end hotels and ryokan, including facilities that don't exist on Booking.com or Expedia; ratings and price levels by area.
• Hotel revenue management & rate shopping — monitor the luxury segment's advertised prices by area; inbound-record tourism and rising ADRs make Japanese OTA price data valuable.
• Market research & real estate — luxury hospitality supply, price levels, room counts and ratings by region; onsen/ryokan segment analyses with geo coordinates.
• Data teams — a stable English schema over a Japanese-only source, aligned field-for-field with the same developer's jalan.net actor for cross-OTA joins.

Sample output (dataset item)

{
  "hotelName": "ハイアット リージェンシー 京都",
  "hotelType": "hotel",
  "area": "京都駅周辺",
  "largeArea": "京都駅周辺",
  "prefecture": "京都府",
  "prefectureEn": "Kyoto",
  "prefectureCode": "26",
  "address": "京都府京都市東山区三十三間堂廻り644番地2",
  "postalCode": "605-0941",
  "latitude": 34.988512,
  "longitude": 135.773391,
  "rating": 4.08,
  "reviewCount": 17,
  "minPriceJpy": 44748,
  "maxPriceJpy": null,
  "priceBasis": "total JPY, tax included — lowest advertised price for 2 adult(s), 1 night(s), 1 room(s), undated (ikyu.com default search); point discounts not applied",
  "plans": [
    { "planName": null, "roomType": null, "meal": "食事なし", "pricePerPersonJpy": 22374, "priceTotalJpy": 44748 }
  ],
  "totalRooms": 187,
  "checkinTime": "15:00",
  "checkoutTime": "12:00",
  "onsen": false,
  "amenities": ["GymFitnessEquipment", "AirportShuttle"],
  "url": "https://www.ikyu.com/00001116/",
  "detailFetched": true,
  "source": "一休.com (ikyu.com)",
  "sourceUrl": "https://www.ikyu.com/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-25T09:12:44Z"
}

Input reference

{
  "prefecture": "Kyoto",
  "area": "京都駅",
  "keyword": "リッツ",
  "accommodationType": "hotel",
  "includeDetails": true,
  "maxItems": 50,
  "maxApiRequests": 120
}

• prefecture (required): English name of one of the 47 prefectures exactly as in the dropdown ("Kyoto", "Tokyo", "Hokkaido" …). The Apify platform validates this list before the run starts, so "京都府", "26" or "kyoto-fu" are rejected immediately with the list of valid values. Cities/resorts are not prefectures — "Hakone" is rejected; use "Kanagawa" + "area": "箱根".
• area (optional): an ikyu area code (ma026005) or a substring of the Japanese area name (京都駅); an unknown value stops the run with the prefecture's full area list. Leave empty for all areas.
• keyword (optional): client-side substring filter on the facility name.
• accommodationType (default all): hotel / ryokan / villa.
• includeDetails (default false) / maxItems (default 10, max 10000) / maxApiRequests (default 120, max 300) / proxyConfiguration (default RESIDENTIAL, country JP — required, see FAQ).

Pricing

Pay per result — see the pricing tab. One prefecture area is typically tens to a few hundred facilities (ikyu is curated, so counts are smaller and more selective than mass-market OTAs).

FAQ

Where does the data come from? Live from ikyu.com's public, login-free area listing and facility pages at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

Is this an official ikyu.com / LY Corporation service? No. Unofficial, independently built and maintained, and not affiliated with or endorsed by Ikyu Corporation or LY Corporation. It reads only publicly available pages that ikyu.com's robots.txt leaves open to general crawlers.

Are reviews included? Only the numeric rating average and review count. Review texts and reviewer names are never extracted — deliberately: review prose is user-generated copyrighted content and can contain personal data. The same applies to the hotels' own marketing prose (catch copies/descriptions) and published phone numbers, which stay on the source site. This keeps the output strictly factual business data, with no personal data (GDPR-relevant collection: none).

Who is responsible for how the data is used? You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms) is your responsibility as the user.

Can I search for a specific check-in date? No — by design. ikyu.com's robots.txt disallows its dated search endpoints to crawlers, so this Actor only reads the robots-open undated listings: each facility's lowest advertised price for the site-default party (2 adults, 1 night, 1 room), before point discounts. Treat prices as a snapshot and re-run for fresh data.

Do I need a proxy? Yes — and it is on by default. ikyu.com answers HTTP 403 to requests from datacenter IP ranges (observed 2026-08-25 for both direct Apify runs and Apify's datacenter proxy), while the same requests succeed from ordinary consumer connections. The default proxyConfiguration therefore uses Apify Residential proxies with country JP; leave it as is for reliable runs. Residential proxy bandwidth is billed as Apify platform usage on top of the Actor price. The Actor never rotates identities or evades blocks on its own: one residential egress IP is used for the whole run. If ikyu.com refuses a request mid-crawl (403/429/5xx), the run keeps the records it already collected, ends successfully with complete: false and a stopReason in RUN_SUMMARY, and you are billed only for the records actually delivered. A run that is blocked before its first record still fails visibly.

What about server load? Strictly serial requests, ≥1.2 s apart, 20 facilities per list page, one optional extra request per facility detail, hard per-run request budget (max 300), exponential backoff, no CAPTCHA/login/block evasion. If ikyu.com changes its page format, the Actor stops instead of silently mis-parsing. A stop that happens after some records were already collected ends the run successfully with complete: false and a stopReason; a stop before the first record fails the run visibly.

Search terms this Actor answers

ikyu scraper · ikyu.com scraper · japan luxury hotels data · luxury ryokan data · japan hotel prices api · ryokan booking data · japan luxury travel data · 一休 データ · high-end hotel japan dataset · japan 5 star hotels list · kyoto luxury ryokan prices · japan hotel rate shopping · japanese OTA data

More Japan data Actors by the same developer

• Japan Hotels & Ryokan Prices (jalan.net) — the mass-market counterpart: same schema, Japan's largest domestic OTA.
• Japan Hotels & Ryokan (Yahoo! Travel) — travel.yahoo.co.jp listings: same schema, a third OTA for cross-OTA joins.
• Japan Government Tenders & Awards — tender notices and award results from the kkj.go.jp portal.
• Japan Medical Facilities — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
• Japan Care Facilities — long-term care providers across 35 service types (MHLW open data, CC BY).
• Japan Government Subsidies & Grants — open subsidy calls from the official jGrants API.
• Japan Renewable Energy FIT/FIP Facilities — METI-certified renewable installations, privacy-safe schema.
• Japan Financial Licenses & Registrations — FSA-licensed banks, securities firms, crypto exchanges and more.
• Japan Construction & Real-Estate Licenses — licensed contractors and brokers from MLIT's official register.
• Japan Trade Statistics — monthly import/export flows by HS code and partner country, from Japan Customs.

---

Unofficial tool; not affiliated with Ikyu Corporation or LY Corporation. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data is collected.