Japan Hotels & Ryokan Prices (jalan.net)

Japanese hotels and ryokan with per-person prices, plan lists, ratings and facility facts — from jalan.net, Japan's largest domestic travel booking site, in a clean English schema.

This Actor searches jalan.net's public hotel listings by prefecture and area and returns each facility as English-schema JSON: name, facility type (hotel/ryokan/pension/…), area and prefecture (with JIS code and English name), full address and postal code, guest rating and review count, per-person price range in JPY (tax included), the advertised stay plans (plan name, room type, meal condition, price), room count, check-in/out times, onsen flag and amenity list. Prices can be undated (each facility's lowest advertised price) or for a concrete check-in date, nights and guest count.

Many Japanese hotels and most traditional ryokan sell primarily — sometimes exclusively — through jalan.net, and the site is Japanese-only and Shift-JIS encoded, which makes it invisible to most international tooling. This Actor is the bridge.

Unofficial tool. Not affiliated with or endorsed by Recruit Co., Ltd. or jalan.net. 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), and extracts factual business data only — no review texts, no reviewer names, 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 hotels around Kyoto Station with detail pages, ~30 seconds):

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

Common input mistakes

Wrong	Right	Why
"prefecture": "Kyoto-shi" / "Hakone" / "Kobe"	"prefecture": "Kyoto" / "Kanagawa" / "Hyogo"	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": "Arashiyama"	"area": "嵐山" (or the LRG code from a jalan 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.
"checkin": "15/09/2026" or a past date	"checkin": "2026-09-15" (today or later), or omit it	ISO date; undated runs return each facility's lowest advertised price.
"maxItems": "50"	"maxItems": 50	Numbers are numbers in JSON — the platform rejects a numeric string before the run starts.

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 (it is a client-side substring filter — try a shorter Japanese fragment such as 温泉), a checkin date on which every facility in the area is sold out, or a small maxApiRequests with a rare keyword. Widen the query and re-run.

---

Who is this for?

• Hotel revenue management & rate shopping — monitor competitors' jalan.net prices by area and date; inbound-record tourism and rising ADRs make Japanese OTA price data valuable, and jalan-only ryokan never show up on Booking.com.
• Travel startups & OTAs — build inventory awareness of the Japanese domestic market, including facilities that don't exist on international platforms.
• Market research & real estate — hospitality supply, price levels, and ratings by region; onsen/ryokan segment analyses.
• Data teams — a stable English schema over a Shift-JIS, Japanese-only source.

Sample output (dataset item)

{
  "hotelName": "ロイヤルツインホテル京都八条口 ～みやびの湯～",
  "hotelType": "hotel",
  "area": "京都駅前",
  "largeArea": "京都駅周辺",
  "prefecture": "京都府",
  "prefectureEn": "Kyoto",
  "prefectureCode": "26",
  "address": "京都府京都市南区東九条室町４６－２",
  "postalCode": "601-8001",
  "rating": 4.7,
  "reviewCount": 2009,
  "minPriceJpy": 5880,
  "maxPriceJpy": 9724,
  "priceBasis": "per-person JPY, tax included — lowest advertised prices (no stay dates given)",
  "stay": null,
  "plans": [
    { "planName": "【朝食付き】スタンダードプラン", "roomType": "ツイン", "meal": "朝のみ", "pricePerPersonJpy": 9724, "priceTotalJpy": 19448 }
  ],
  "totalRooms": 219,
  "checkinTime": "15:00～",
  "checkoutTime": "～11:00",
  "onsen": true,
  "amenities": ["玄関前の車椅子用スロープ", "客室内車椅子可"],
  "access": "京都駅「中央改札口」を出て「八条西口」出口から徒歩約2分",
  "url": "https://www.jalan.net/yad358756/",
  "detailFetched": true,
  "source": "じゃらんnet (jalan.net)",
  "sourceUrl": "https://www.jalan.net/",
  "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": "温泉",
  "checkin": "2026-10-01",
  "nights": 1,
  "guests": 2,
  "includeDetails": true,
  "maxItems": 50,
  "maxApiRequests": 60
}

• 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): a jalan LRG area code (260500 / LRG_260500) 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.
• checkin / nights / guests (optional): dated pricing; leave checkin empty for each facility's lowest advertised (undated) prices.
• includeDetails (default true) / maxItems (default 10, max 10000) / maxApiRequests (default 30, max 60) / proxyConfiguration (default none).

Pricing

Pay per result — see the pricing tab. One prefecture area is typically tens to a few hundred facilities.

FAQ

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

Is this an official jalan.net / Recruit service? No. Unofficial, independently built and maintained, and not affiliated with or endorsed by Recruit Co., Ltd. It reads only publicly available pages.

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-phrases/descriptions), which stays 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.

Are prices accurate? Prices are what jalan.net advertised at retrieval time, per person, tax included, for the searched conditions (or the undated lowest advertised price). They change constantly — treat them as a snapshot, and re-run for fresh data.

What about server load? Strictly serial requests, ≥1.2 s apart, ~30 facilities per list page, one extra request per facility detail, hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If jalan.net changes its page format or refuses a request mid-crawl (403/429/5xx), 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 in RUN_SUMMARY, and you are billed only for the records actually delivered; a stop before the first record fails the run visibly.

Search terms this Actor answers

jalan scraper · jalan.net scraper · Japan hotel prices data · Japan hotel scraper · ryokan data · Japanese OTA prices · Japan hotel market data · 宿泊料金 データ · Japan travel accommodation dataset · onsen ryokan list · Kyoto hotel prices · Japan hotel rate shopping

More Japan data Actors by the same developer

• Japan Luxury Hotels & Ryokan (ikyu.com) — the curated luxury OTA: same schema, high-end hotels and ryokan.
• 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 Recruit Co., Ltd. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data is collected.