# Rakuten Travel Scraper: Japan Hotels, Rates & Reviews (`abotapi/rakuten-travel-scraper`) Actor

Scrape Rakuten Travel, Japan's largest domestic hotel-booking site, by prefecture, keyword or URL. Every row carries name, rating, review count, lowest price and access, with optional details: address, phone, facilities, policies, photos and reviews. No API key needed.

- **URL**: https://apify.com/abotapi/rakuten-travel-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 hotel records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Rakuten Travel Scraper: Japan Hotels, Rates & Reviews

Scrape **Rakuten Travel** (travel.rakuten.co.jp), Japan's largest domestic
hotel-booking site, into clean structured rows. Search by prefecture, run the
site's own keyword search, or paste hotel, area, keyword-results or day-use
listing URLs you already have. Every row carries name, rating, review count,
lowest price, catch copy and access, and can be enriched from the hotel's own
pages: address, phone, check-in times, facilities, credit cards, cancellation
policies, photos, the review summary and individual review texts.

Built for price monitoring, market research, inventory tracking and review
mining across all 47 prefectures. No API key, no application registration, no
account needed: the actor reads the site's own public pages directly.

***

### Why This Scraper?

- Around 40 fields per hotel, from the listing card through full detail and
  review pages
- Three input modes: prefecture walk, keyword search, or any pasted hotel,
  area, keyword-results or day-use URL
- The site's own server-side price and review sorts, plus client-side price
  bounds and a minimum rating filter
- Review mining: overall score, per-category averages (room, service,
  location, meals, bath), star histogram and review texts
- Resume and incremental modes for daily scheduled monitoring of the same
  scope, returning only what changed
- Covers all 47 prefectures of the site's own area tree, with the declared
  result totals respected page by page
- Bilingual input: Japanese prefecture names (東京, 北海道) and romaji
  (tokyo, hokkaido) both work

### Data You Get

> Sample shape: values are illustrative placeholders, not from a live hotel.

| Field | Example value |
|---|---|
| `hotelNo` | `0000000` |
| `name` | `Sample Seaside Hotel` |
| `url` | `https://travel.rakuten.co.jp/HOTEL/0000000/0000000.html` |
| `ratingValue` | `4.2` |
| `reviewCount` | `1200` |
| `minPriceYen` | `8000` |
| `minPriceTaxIncludedYen` | `8800` |
| `catchcopy` | `A sample one line catch copy from the listing card` |
| `access` | `Sample station: 5 min on foot` |
| `thumbnailUrl` | `https://trvimg.r10s.jp/share/image_up/0000000/sample.jpg` |
| `address` | `〒000-0000 Sample prefecture Sample city 1-2-3` |
| `phoneNumber` | `000-000-0000` |
| `checkInTime` | `15:00〜19:00` |
| `checkOutTime` | `10:00` |
| `parking` | `Available, 50 cars` |
| `facilities` | `["Restaurant", "Large bath", "Non-smoking rooms"]` |
| `cancellationPolicy` | `Cancellation terms as printed on the page` |
| `description` | `Full property description text when details are on` |
| `ratingSummary` | `{"overallScore": 4.2, "reviewCount": 1200, "categoryAverages": {"ROOM": 4.1}}` |
| `reviews` | ` [{"title": "Sample review title", "comment": "Sample review text", "score": 5}]` |
| `reviewsTotal` | `1200` |
| `changeType` | `NEW` |
| `changedFields` | `["minPriceYen"]` |

### How to Use

Search one prefecture, with full details (default):

```json
{
  "mode": "search",
  "locations": ["東京"],
  "maxItems": 20
}
```

Prefecture walk with the site's own price sort, keyword searches and price
bounds:

```json
{
  "mode": "search",
  "locations": ["大阪", "kyoto"],
  "keywords": ["温泉 箱根"],
  "sortBy": "price_low",
  "minPriceYen": 6000,
  "maxPriceYen": 25000,
  "minRating": "3.5",
  "maxItems": 60
}
```

Paste hotel URLs for exact fetches (reviews included):

```json
{
  "mode": "url",
  "urls": [
    "https://travel.rakuten.co.jp/HOTEL/0000000/0000000.html",
    "https://travel.rakuten.co.jp/HOTEL/0000001/0000001.html"
  ],
  "fetchReviews": true,
  "maxItems": 10
}
```

Daily price watch of one prefecture (incremental mode returns only changes
after the first run):

```json
{
  "mode": "search",
  "locations": ["沖縄"],
  "maxItems": 0,
  "incrementalMode": true,
  "stateKey": "okinawa-watch"
}
```

### Input Parameters

| Parameter | Type | Default | Description |
|---|---|---|---|
| `mode` | select | `search` | `search` walks prefecture area pages and keyword results; `url` processes pasted URLs. |
| `locations` | array | `["東京"]` | Prefecture words (Japanese or romaji) matched against the site's 47-prefecture area tree. Search mode only. |
| `keywords` | array | `[]` | Keyword searches run on the site's own search, following the site's own results pager (about 30 hotels per page). Search mode only. |
| `urls` | array | `[]` | Hotel URLs (one hotel each), or area `/yado/`, `/ds/yado/`, keyword-results and day-use listing URLs (walked like a search). URL mode only. |
| `sortBy` | select | `recommended` | The site's server-side order of each prefecture walk: recommended, price low/high, review score. Search mode, area walks only. |
| `minPriceYen` | integer | - | Keep rows at or above this price in yen. Both modes. |
| `maxPriceYen` | integer | - | Keep rows at or below this price in yen. Both modes. |
| `minRating` | string | - | Keep rows whose review score is at least this (for example 4.0). Both modes. |
| `sortResultsBy` | select | `site_order` | Reorder this run's collected rows after the read. Both modes. |
| `fetchDetails` | boolean | `true` | Read each hotel's own page for address, phone, check-in times, facilities, policies and photos. Adds the per-hotel detail enrichment charge. |
| `fetchReviews` | boolean | `false` | Also read the review page: summary, per-category averages and review text. Covered by the same enrichment charge. |
| `maxReviews` | integer | `20` | Maximum review rows per hotel when `fetchReviews` is on. `0` = all available reviews. The enrichment event is charged once for each started block of 10 returned review rows. |
| `maxItems` | integer | `20` | The single output cap across all sources. `0` = unlimited. |
| `maxPages` | integer | `0` | Safety bound on listing pages per source. `0` = no page limit. |
| `resumeFromRunId` | string | - | Continue one interrupted run: skip records that run already collected. |
| `incrementalMode` | boolean | `false` | Scheduled monitoring: return only NEW, UPDATED and REAPPEARED records against the previous run of the same scope. |
| `stateKey` | string | - | Optional name for an incremental monitoring campaign. |
| `emitUnchanged` | boolean | `false` | Also return UNCHANGED rows (billed). |
| `emitExpired` | boolean | `false` | Also return EXPIRED rows after a complete scan (billed). |
| `proxy` | object | standard proxy | The default standard Apify proxy serves every page this actor reads. |
| `mcpConnectors` | array | `[]` | Optional MCP connector IDs for the condensed result export. |
| `notionParentPageUrl` | string | - | Optional Notion parent page URL for the MCP export. |
| `maxNotifyListings` | integer | `50` | Maximum condensed records sent to MCP connectors per run. |

### Output Example

> Sample shape: values are illustrative placeholders, not from a live hotel.

```json
{
  "recordId": "0000000",
  "hotelNo": "0000000",
  "rowType": "hotel",
  "url": "https://travel.rakuten.co.jp/HOTEL/0000000/0000000.html",
  "name": "Sample Seaside Hotel",
  "ratingValue": 4.2,
  "reviewCount": 1200,
  "minPriceYen": 8000,
  "minPriceTaxIncludedYen": 8800,
  "catchcopy": "A sample one line catch copy from the listing card",
  "access": "Sample station: 5 min on foot",
  "position": 3,
  "searchSource": "東京",
  "address": "〒000-0000 Sample prefecture Sample city 1-2-3",
  "phoneNumber": "000-000-0000",
  "faxNumber": "000-000-0001",
  "checkInTime": "15:00〜19:00",
  "checkOutTime": "10:00",
  "parking": "Available, 50 cars",
  "totalRooms": 120,
  "facilities": ["Restaurant", "Large bath", "Non-smoking rooms"],
  "roomAmenities": ["TV", "Refrigerator", "Hair dryer"],
  "creditCards": ["VISA", "Master Card"],
  "meals": ["[Breakfast] Restaurant"],
  "cancellationPolicy": "Sample cancellation terms from the hotel page",
  "description": "Sample full property description.",
  "photoUrls": ["https://trvimg.r10s.jp/share/image_up/0000000/sample.jpg"],
  "ratingSummary": {
    "overallScore": 4.2,
    "reviewCount": 1200,
    "categoryAverages": {"ROOM": 4.1, "BREAKFAST": 4.3},
    "starHistogram": {"FIVE": 500, "FOUR": 400}
  },
  "reviews": [
    {
      "reviewId": "000000",
      "title": "Sample review title",
      "comment": "Sample review text.",
      "postedAt": "2026-01-01T00:00:00Z",
      "score": 5,
      "nickname": "SampleNick",
      "stayDate": "2026-01-01",
      "planName": "Sample plan name"
    }
  ],
  "reviewsTotal": 1200,
  "scrapedAt": "2026-01-01T00:00:00Z",
  "changeType": "NEW",
  "changedFields": [],
  "firstSeenAt": "2026-01-01T00:00:00Z",
  "lastSeenAt": "2026-01-01T00:00:00Z"
}
```

### Send results into your apps (MCP connectors)

Optionally pipe this actor's results into the apps you already use with MCP
connectors: authorize one under Apify, Settings, API & Integrations, then
select it in the `mcpConnectors` input and set `notionParentPageUrl` for
Notion. Each connector receives a condensed summary per record (a title plus
key fields flattened to text, `maxNotifyListings` per run), not the full
record; the complete record always stays in the Apify dataset. Leave the
inputs empty and nothing changes: the export never runs and the dataset
output is identical.

### Plan Requirement

- Works on any Apify plan, including the free tier. Per-event pricing is shown
  on the actor page before a run.
- Prices are the site's publicly displayed lowest rates for its default
  availability window, in Japanese yen; a rate move between scheduled runs
  classifies as UPDATED in incremental mode.
- Keyword searches follow the site's own results pager (about 30 hotels per
  page). Prefecture walks follow the site's own pager, 30 hotels per page.
- The keyword results page is served in the site's legacy Japanese text
  encoding; the actor encodes your keywords and decodes the page for you.
- A run needs no account and no API registration on any surface it reads.

# Actor input Schema

## `mode` (type: `string`):

How to start the scrape. 'search' walks the site's own area listing pages for the prefectures you list, and runs the keyword searches you list. 'url' processes the Rakuten Travel URLs you paste: a hotel URL is fetched as a single hotel; an area, keyword-results or day-use listing URL is browsed like a search, its own path deciding the scope.

## `locations` (type: `array`):

One or more Japanese prefecture names or romaji spellings, for example '東京', '大阪', 'okinawa', '北海道'. Each word is matched against the 47 prefectures of the site's own area listing tree, and every matching prefecture is walked independently. Search mode ONLY: in URL mode the pasted URL decides its own scope. Sub-areas of a prefecture (for example a city page) can be scoped by pasting their URL in URL mode.

## `keywords` (type: `array`):

One or more search words, for example '新宿 ホテル' or '温泉 箱根'. Each keyword runs the site's own keyword search and follows the results pages the site's own pager declares (about 30 hotels per page). Search mode ONLY: in URL mode the pasted URLs decide their own scope. The keyword pages are served in the site's legacy text encoding, which the actor handles for you.

## `urls` (type: `array`):

Rakuten Travel URLs to process. A hotel URL (travel.rakuten.co.jp/HOTEL/...) or a plan-page URL (hotel.travel.rakuten.co.jp/hotelinfo/plan/...) returns one hotel. An area listing URL (/yado/... or search.travel.rakuten.co.jp/ds/yado/...), a keyword-results URL (kw.travel.rakuten.co.jp/keyword/Search.do) or a day-use listing URL (/dayuse/...) is paginated like a search, its own path deciding the scope. URL mode only.

## `sortBy` (type: `string`):

The site's own server-side ordering of each prefecture walk: recommended (the site default), price low to high, price high to low, or review score high to low. Search mode ONLY and area walks only: in URL mode the pasted URL decides its own scope, and keyword results come in the site's own order. For reordering this run's collected rows after the read, use the ordering field under Output and limits.

## `minPriceYen` (type: `integer`):

Only keep listing rows whose lowest rate is at least this many Japanese yen. Narrows listing rows in BOTH search mode and URL mode; a pasted hotel URL always returns its hotel.

## `maxPriceYen` (type: `integer`):

Only keep listing rows whose lowest rate is at most this many Japanese yen. Narrows listing rows in BOTH search mode and URL mode; a pasted hotel URL always returns its hotel.

## `minRating` (type: `string`):

Only keep listing rows whose guest review score is at least this value, for example 4.0. Rows whose score the listing page does not show are dropped while this filter is set. Narrows listing rows in BOTH search mode and URL mode; a pasted hotel URL always returns its hotel.

## `sortResultsBy` (type: `string`):

Arranges the rows this run collected, after they are read, including pasted hotels. This is a local tidy up of one run's output, not a catalogue wide ordering. Applies in BOTH search mode and URL mode.

## `fetchDetails` (type: `boolean`):

Read each hotel's own detail page for the complete record: address, phone, fax, access, check-in and check-out times, parking, room count, facilities, room amenities, credit cards, meal options, cancellation policies, description and photos. Leave it on for the full record; turn it off for cheap listing rows only (name, rating, review count, lowest price, catch copy, access, thumbnail). Turning it on adds the Hotel detail enrichment charge per hotel actually read this run.

## `fetchReviews` (type: `boolean`):

Read each hotel's review page as well: the review summary (overall score, per-category averages, star histogram) and review text. The amount is controlled by Max reviews per hotel. Adds review reads covered by the same Hotel detail enrichment charge.

## `maxReviews` (type: `integer`):

Maximum review rows to return for each hotel when Fetch reviews is on. The default is 20. Set 0 to return all reviews available from the site. Billing starts one Hotel detail enrichment event for each block of 10 review rows returned.

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

The single cap on this run: stop after collecting this many records across all prefectures, keywords and URLs. Set 0 for unlimited.

## `maxPages` (type: `integer`):

Safety bound on how many listing pages to walk per prefecture, keyword or pasted area URL. Each page serves about 30 hotels. Leave 0 for no page limit: the run then stops at Max items, or when the site's own pager runs out.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large crawl without returning or charging for records already collected there. Use this after an interrupted or capped run. For recurring monitoring of the same search, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or weekly recurring monitoring of the same scope, for example a prefecture price watch. The first run returns everything matching as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED records. Rate and score moves ARE reported as UPDATED: on a booking site the rate is the signal, not noise. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately per prefecture, keyword, URL and filter setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the prefectures, keywords, URLs and filters, so two different scopes never mix state.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return records that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want a full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return records that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked scope: not when Max items capped it, not when Resume was used, and not when the run was refused. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a page per record; other connectors get a best-effort write or digest. Each connector receives a condensed summary per record, not the full record; the complete record always stays in the dataset. Leave empty to skip; this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL or id of the Notion page under which record pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on records written to each connector per run. Does not affect the dataset.

## `proxy` (type: `object`):

Leave the default: the standard Apify proxy serves every page this actor reads, probed live. Prices quoted on each row are Japanese yen.

## Actor input object example

```json
{
  "mode": "search",
  "locations": [
    "東京"
  ],
  "keywords": [],
  "urls": [
    "https://travel.rakuten.co.jp/HOTEL/70818/70818.html",
    "https://travel.rakuten.co.jp/yado/tokyo/"
  ],
  "sortBy": "recommended",
  "sortResultsBy": "site_order",
  "fetchDetails": true,
  "fetchReviews": false,
  "maxReviews": 20,
  "maxItems": 20,
  "maxPages": 0,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "maxNotifyListings": 50,
  "proxy": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# 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 = {
    "mode": "search",
    "locations": [
        "東京"
    ],
    "keywords": [],
    "urls": [
        "https://travel.rakuten.co.jp/HOTEL/70818/70818.html",
        "https://travel.rakuten.co.jp/yado/tokyo/"
    ],
    "sortBy": "recommended",
    "sortResultsBy": "site_order",
    "fetchDetails": true,
    "fetchReviews": false,
    "maxReviews": 20,
    "maxItems": 20,
    "maxPages": 0,
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "proxy": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/rakuten-travel-scraper").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 = {
    "mode": "search",
    "locations": ["東京"],
    "keywords": [],
    "urls": [
        "https://travel.rakuten.co.jp/HOTEL/70818/70818.html",
        "https://travel.rakuten.co.jp/yado/tokyo/",
    ],
    "sortBy": "recommended",
    "sortResultsBy": "site_order",
    "fetchDetails": True,
    "fetchReviews": False,
    "maxReviews": 20,
    "maxItems": 20,
    "maxPages": 0,
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "proxy": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/rakuten-travel-scraper").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 '{
  "mode": "search",
  "locations": [
    "東京"
  ],
  "keywords": [],
  "urls": [
    "https://travel.rakuten.co.jp/HOTEL/70818/70818.html",
    "https://travel.rakuten.co.jp/yado/tokyo/"
  ],
  "sortBy": "recommended",
  "sortResultsBy": "site_order",
  "fetchDetails": true,
  "fetchReviews": false,
  "maxReviews": 20,
  "maxItems": 20,
  "maxPages": 0,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true
  }
}' |
apify call abotapi/rakuten-travel-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/rakuten-travel-scraper"
        }
    }
}
```

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/4hTZyyzXVxgSIs2N4/builds/P1Lb3gupOGeohTqt0/openapi.json