Japan Hotels & Ryokan (Yahoo! Travel)

Japanese hotels, ryokan and vacation rentals from travel.yahoo.co.jp (Yahoo!トラベル), with ratings, room counts, geo coordinates and advertised prices, in a clean English schema — searchable by prefecture.

This Actor searches Yahoo!トラベル's public listings by prefecture 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 1 adult / 1 night / 1 room). Optional detail fetches add check-in/check-out times, an onsen flag and amenity flags (pool, gym, airport shuttle …).

Yahoo!トラベル is one of Japan's largest domestic OTAs. The site is Japanese-only, which makes its inventory and price data hard to reach from international tooling. This Actor is the bridge, and it uses the same output schema as this developer's jalan.net and ikyu.com Actors so you can join across OTAs field-for-field.

Unofficial tool. Not affiliated with or endorsed by LY Corporation (Yahoo! JAPAN / Yahoo!トラベル). 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, run. This exact input is verified (SUCCEEDED, items > 0):

{
  "prefecture": "Kyoto",
  "maxItems": 30
}

Running with no input at all also works (same defaults, Apify RESIDENTIAL proxy JP on by default). prefecture is a dropdown of the 47 English prefecture names; via the API you may also pass the Japanese name ("京都府"), the JIS code ("26"), or common romanisations ("osaka-fu", "Ōsaka", "Tokyo-to").

Who is this for?

• Travel agencies & OTAs — inventory and price awareness across Japanese hotels and ryokan by area; a stable English feed over a Japanese-only source.
• Hotel revenue management & rate shopping — monitor advertised prices by area; inbound tourism and rising ADRs make Japanese OTA price data valuable.
• Market research & real estate — hospitality supply, price levels, room counts and ratings by region; onsen/ryokan segment analyses with geo coordinates.
• Data teams — a stable English schema aligned field-for-field with the same developer's jalan.net and ikyu.com Actors for cross-OTA joins.

Sample output (dataset item)

{
  "hotelName": "Smart Stay SHIZUKU 上野駅前",
  "hotelType": "hotel",
  "area": "上野",
  "largeArea": "東京",
  "prefecture": "東京都",
  "prefectureEn": "Tokyo",
  "prefectureCode": "13",
  "address": "東京都台東区上野2-13-11",
  "postalCode": "110-0005",
  "latitude": 35.710148,
  "longitude": 139.773175,
  "rating": 4.36,
  "reviewCount": 214,
  "minPriceJpy": 3880,
  "maxPriceJpy": null,
  "priceBasis": "total JPY, tax included — lowest advertised price for 1 adult(s), 1 night(s), 1 room(s), undated (Yahoo!トラベル default search); point discounts not applied",
  "plans": [
    { "planName": null, "roomType": null, "meal": "食事なし", "pricePerPersonJpy": 3880, "priceTotalJpy": 3880 }
  ],
  "totalRooms": 210,
  "checkinTime": null,
  "checkoutTime": null,
  "onsen": null,
  "amenities": null,
  "url": "https://travel.yahoo.co.jp/00910827/",
  "detailFetched": false,
  "source": "Yahoo!トラベル (travel.yahoo.co.jp)",
  "sourceUrl": "https://travel.yahoo.co.jp/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-26T00:12:44Z"
}

Input example

{
  "prefecture": "Kyoto",
  "area": "祇園",
  "accommodationType": "ryokan",
  "maxItems": 50
}

prefecture is required (JIS code, Japanese or English name). area narrows to a Japanese area-name substring (e.g. 祇園, 神戸, 上野). accommodationType filters to hotels, ryokan, or villas. keyword filters on the facility name.

How it works (and why there is no check-in date)

Yahoo!トラベル organizes its site by region, not by individual prefecture, so this Actor enters at the Yahoo region hub that contains the requested prefecture (e.g. Kyoto → the 近畿（大阪以外） hub) and filters the region's hotels down to the requested prefecture using each listing's own prefecture field. For a prefecture that is one of several in its region, deeper paging may be needed; raise maxApiRequests or narrow with area for large regions.

The Actor reads only the undated listings (the site-default lowest price for 1 adult / 1 night / 1 room). Yahoo!トラベル's robots.txt disallows its dated search endpoints and date-conditioned URL patterns to crawlers, so a check-in-date input is deliberately not offered — the Actor stays strictly on the robots-open pages. Treat prices as a snapshot and re-run for fresh data.

Common input mistakes

Mistake	Correct
"prefecture": "Kyoto-shi" / "Osaka City" / "Yokohama" (a city)	"prefecture": "Kyoto" / "Osaka" / "Kanagawa" — prefectures only; narrow with area
"prefecture": "Kansai" (a region)	one prefecture at a time, e.g. "Osaka"
"area": "Gion" (romaji)	"area": "祇園" — area names are matched in Japanese
"accommodationType": "onsen" / "castle"	"hotel", "ryokan" or "villa" (inn, 旅館, vacation-rental are accepted aliases)
turning the proxy off	keep the default RESIDENTIAL/JP proxy — datacenter IPs get HTTP 403
"maxItems": "all"	a number, e.g. 30

Empty results?

A run that finds nothing completes with 0 items and a warning in the log (not a failure). Typical causes: an area substring that does not appear in Yahoo's Japanese area labels (try a shorter string, e.g. 祇園 instead of 祇園四条), a keyword in a script the facility name does not use, or a prefecture that shares a Yahoo region hub with larger neighbours so that its listings sit beyond the request budget — raise maxApiRequests (up to 100) or drop area/keyword and retry.

Pricing

Pay per result — see the pricing tab. Each dataset item is one facility.

FAQ

Where does the data come from? Live from Yahoo!トラベル's public, login-free region/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 Yahoo!トラベル / LY Corporation service? No. Unofficial, independently built and maintained, and not affiliated with or endorsed by LY Corporation. It reads only publicly available pages that Yahoo!トラベル'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. Yahoo!トラベル'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 (1 adult, 1 night, 1 room), before point discounts.

Do I need a proxy? Yes — and it is on by default. Yahoo!トラベル answers HTTP 403 to requests from datacenter IP ranges (observed 2026-08-26 for a direct Apify run), while the same honest requests succeed from ordinary consumer connections. The default proxyConfiguration therefore uses Apify Residential proxies with country JP; leave it as is for reliable runs (a Kyoto smoke test completed cleanly this way). 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 Yahoo!トラベル 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 100), exponential backoff, no CAPTCHA/login/block evasion. If Yahoo!トラベル 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

yahoo travel scraper · yahoo travel japan scraper · japan hotel prices · japan hotel prices api · japan ryokan data · ryokan booking data · japanese OTA data · japan hotel rate shopping · ヤフートラベル データ · japan hotels dataset · japan onsen ryokan prices · japan hotel data by prefecture

More Japan data Actors by the same developer

• Japan Luxury Hotels & Ryokan (ikyu.com) — the curated luxury OTA: same schema.
• Japan Hotels & Ryokan Prices (jalan.net) — Japan's largest domestic OTA: same schema.
• 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 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.