# Japan Hotels & Ryokan (Yahoo! Travel) (`jpopendata/japan-hotels-yahoo-travel`) Actor

Japanese hotels & ryokan with ratings and advertised prices from travel.yahoo.co.jp, by prefecture, in a clean English schema. Unofficial; not affiliated with LY Corporation.

- **URL**: https://apify.com/jpopendata/japan-hotels-yahoo-travel.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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.

***

### 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)

```json
{
  "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

```json
{
  "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.

### 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, on Apify. 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. Set `proxyConfiguration` to Apify **Residential** proxies with country **JP** for reliable runs (a Kyoto smoke test completed cleanly this way). The Actor never rotates identities or evades blocks on its own — a persistent 403/429 fails the run 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 with a clear error instead of silently mis-parsing; if it blocks persistently, the run fails 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.*

# Actor input Schema

## `prefecture` (type: `string`):

REQUIRED. Prefecture to search: JIS code ("26"), Japanese ("京都府") or English ("Kyoto"). Selects the Yahoo!トラベル region hub that contains the prefecture; results are filtered to the prefecture.

## `area` (type: `string`):

Optional area filter, applied client-side as a substring of the published area name (e.g. "祇園", "神戸", "上野"). Leave empty to include every area of the prefecture.

## `keyword` (type: `string`):

Optional case-insensitive substring filter on the facility name (Japanese or English), applied client-side.

## `accommodationType` (type: `string`):

Optional facility-type filter, applied client-side on Yahoo's published type: "hotel" (city/business/resort/capsule hotels), "ryokan" (traditional inns), or "villa" (vacation rentals). Leave as "all" for every type.

## `includeDetails` (type: `boolean`):

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 Yahoo!トラベル.

## `maxItems` (type: `integer`):

Stop after this many dataset records.

## `maxApiRequests` (type: `integer`):

Hard budget of HTTP requests to travel.yahoo.co.jp for this run (region list pages of 20 facilities + 1 per facility detail if enabled). Requests are strictly serial with >= 1.2 s spacing. A prefecture that is one of several in its Yahoo region may need more pages, since the region's other prefectures are filtered out. When the budget runs out the run completes with complete=false in RUN\_SUMMARY.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. travel.yahoo.co.jp answers HTTP 403 to Apify datacenter IP ranges, so RESIDENTIAL proxies with country JP are required for reliable runs on the platform. Never used for rotation/evasion — one client identity per run.

## Actor input object example

```json
{
  "prefecture": "Kyoto",
  "area": "祇園",
  "keyword": "リッツ",
  "accommodationType": "all",
  "includeDetails": false,
  "maxItems": 30,
  "maxApiRequests": 50
}
```

# Actor output Schema

## `records` (type: `string`):

Structured hotel/ryokan records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "prefecture": "Kyoto",
    "maxItems": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-hotels-yahoo-travel").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "prefecture": "Kyoto",
    "maxItems": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-hotels-yahoo-travel").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "prefecture": "Kyoto",
  "maxItems": 30
}' |
apify call jpopendata/japan-hotels-yahoo-travel --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-hotels-yahoo-travel"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/QBhCGLea8BPGwggQ7/builds/1GYRHx7CuUWr530Ob/openapi.json