Japan Rakuten Product & Hotel Search (Official API)

Search Japan's Rakuten Ichiba product catalogue and Rakuten Travel hotels through the official Rakuten Web Service APIs (JSON) — clean, structured records: price, shop, genre, points, review score, stock; hotel min-charge, location, review score, access.

This Actor is a thin, polite client for the official Rakuten Web Service APIs (openapi.rakuten.co.jp): the Rakuten Ichiba Item Search API and the Rakuten Travel SimpleHotelSearch API. It is not a scraper — it calls the documented JSON APIs the way Rakuten intends, using your own Rakuten application ID, and returns each hit as a flat record with a legal envelope (source / sourceUrl / license / retrievedAt) on every item.

Unofficial tool. Independently built and maintained. Not affiliated with, endorsed by, or connected to Rakuten Group, Inc. "Rakuten", "楽天市場", and "楽天トラベル" are trademarks of their respective owners. Every record carries the credit Supported by Rakuten Developers that the Rakuten Web Service terms require.

---

Quick start — verified input

Copy, paste, replace the keys, run (verified against mock API fixtures in npm test; a live run needs your own application ID — see the next section for how to get one in two minutes):

{
  "mode": "ichiba_items",
  "applicationId": "<your key>",
  "accessKey": "<your key>",
  "keyword": "緑茶",
  "maxItems": 100
}

Get both values at https://webservice.rakuten.co.jp/ (free; Rakuten ID needed) → アプリID発行 → the dashboard shows the アプリID (applicationId) and アクセスキー (accessKey). For hotels use {"mode": "travel_hotels", "middleClassCode": "tokyo", ...}.

⚠️ You need your own Rakuten application ID (and access key)

This Actor does not bundle an API key. You must supply your own free Rakuten application ID (and, on the current endpoint versions, an access key) in the applicationId / accessKey inputs.

1. Sign in with a Rakuten member account.
2. Register an application at https://webservice.rakuten.co.jp/ (a developer may register up to 5 apps).
3. Copy your applicationId and accessKey from the app dashboard into this Actor's inputs (both are stored as secrets and redacted from all logs).

Why this design? The Rakuten Web Service terms bind API usage — including the ~1 request/second rate limit and the commercial-use rules — to the application-ID holder. By running under your ID, every call stays inside your own Rakuten Web Service agreement, and there is no shared-key ownership problem.

Terms you are responsible for (please read)

You are the API user, so compliance with the Rakuten Web Service 利用規約 is your responsibility. Two clauses matter most:

• 第10条(4) — you may earn income from this data only via Rakuten Affiliate (or with Rakuten's explicit permission). This Actor supports that sanctioned path: set affiliateId and every record gains an affiliateUrl.
• 第10条(9) — you must not store the retrieved information "in a place that enables sharing with unspecified and/or many people" (i.e. no public redistribution). The Actor writes results to your own private Apify dataset; keep them private.
• 第13条 (credit) — display Supported by Rakuten Developers when you use the data. It is embedded verbatim in the license field of every record.

If your use case does not fit these terms (e.g. reselling the raw data publicly), this Actor is not the right tool.

Two modes

Set mode:

• ichiba_items — Rakuten Ichiba product search. At least one of keyword / genreId / itemCode / shopCode is required. Optional minPrice / maxPrice, sort.
• travel_hotels — Rakuten Travel hotel/ryokan search. At least one of: middleClassCode (prefecture) [+ smallClassCode / detailClassCode], or latitude + longitude [+ searchRadius], or hotelNo.

Discover Rakuten's genre IDs and Travel area class codes with Rakuten's own genre-search / GetAreaClass APIs.

Sample output — Ichiba (dataset item)

{
  "itemName": "静岡県産 深蒸し緑茶 100g 3袋セット",
  "itemCode": "storeaaa:greentea-100g-3set",
  "priceJpy": 1980,
  "shopName": "静岡茶園 楽天市場店",
  "shopCode": "storeaaa",
  "genreId": "100227",
  "janCode": null,
  "availability": "in_stock",
  "pointRate": 1,
  "reviewAverage": 4.55,
  "reviewCount": 231,
  "imageUrl": "https://thumbnail.image.rakuten.co.jp/@0_mall/storeaaa/x_m.jpg",
  "itemUrl": "https://item.rakuten.co.jp/storeaaa/greentea-100g-3set/",
  "affiliateUrl": null,
  "source": "楽天ウェブサービス（楽天市場商品検索API／楽天トラベル施設検索API） / Rakuten Web Service (Rakuten Group, Inc.)",
  "sourceUrl": "https://webservice.rakuten.co.jp/documentation/ichiba-item-search",
  "license": "Supported by Rakuten Developers（…第13条に基づく表示）。… unofficial, not affiliated with … Rakuten Group, Inc. …",
  "retrievedAt": "2026-08-26T09:12:44Z"
}

Sample output — Travel (dataset item)

{
  "hotelName": "新宿グランドホテル",
  "hotelNo": "143637",
  "prefecture": "東京都",
  "city": "新宿区",
  "minChargeJpy": 8800,
  "reviewAverage": 4.12,
  "reviewCount": 1204,
  "access": "JR新宿駅 東口より徒歩5分",
  "hotelSpecial": "全室Wi-Fi無料。新宿駅至近のビジネスホテル。",
  "latitude": 128010.5,
  "longitude": 502340.2,
  "imageUrl": "https://img.travel.rakuten.co.jp/image/hotel/143637_m.jpg",
  "hotelInfoUrl": "https://img.travel.rakuten.co.jp/HOTEL/143637/143637.html",
  "affiliateUrl": null,
  "source": "楽天ウェブサービス…",
  "sourceUrl": "https://webservice.rakuten.co.jp/documentation/simple-hotel-search",
  "license": "Supported by Rakuten Developers…",
  "retrievedAt": "2026-08-26T09:12:44Z"
}

reviewAverage/reviewCount are the numeric review score and count only — review text, reviewer names, and hotel/shop phone numbers are never retrieved. Missing values are null (not zero-filled or empty-stringed).

Input example

{
  "mode": "ichiba_items",
  "applicationId": "<your key>",
  "accessKey": "<your key>",
  "keyword": "緑茶",
  "minPrice": 500,
  "maxPrice": 3000,
  "sort": "-reviewCount",
  "maxItems": 200
}

Common input mistakes

Mistake	Correct
"applicationId": "<your key>" left as is / empty	paste your real 19-digit アプリID (the run fails immediately with a link to get one)
"keyword": "緑茶" with "mode": "travel_hotels"	keyword is an Ichiba field — use "mode": "ichiba_items", or give middleClassCode for hotels
"middleClassCode": "Tokyo" / "東京都"	lower-case romaji class code: "tokyo" (upper case is folded for you; kanji is not)
"latitude": 35.69 without longitude	both coordinates together, decimal degrees
"searchRadius": 10	0.1–3.0 km
"sort": "price" / "newest"	accepted — canonical tokens are +itemPrice, -itemPrice, -reviewCount, -updateTimestamp …

Empty results?

A run that finds nothing completes with 0 items and a warning in the log (not a failure). Typical causes: an English keyword for a product listed only in Japanese (try 緑茶 instead of green tea), a shopCode/genreId/itemCode that does not exist, a Travel smallClassCode that does not belong to the given middleClassCode, or a geo search in an area with no Rakuten Travel facilities within the radius. Broaden the query or drop a filter and retry. HTTP 400 wrong_parameter with a valid key usually means a class code is misspelled; 401/403 means the application ID / access key is wrong.

Affiliate links (optional & recommended)

Set affiliateId (your Rakuten affiliate ID) and each record will include an affiliateUrl. This is the income path Rakuten's terms permit (第10条(4)).

Pricing

Pay per result — see the pricing tab. Note the Rakuten API's own limit of ~1 request per second per application; this Actor spaces requests ≥ 1.1 s apart and pages 30 hits per request, so a few hundred items take a minute or two.

FAQ

Is this official? No. Unofficial, not affiliated with Rakuten Group. It is a client of Rakuten's official public Web Service APIs.

Do you store or resell Rakuten's data? No. The Actor fetches results live under your application ID and writes them to your Apify dataset. You are the API user; the data lands in your account. Keep it private (第10条(9)) and keep the Supported by Rakuten Developers credit (embedded in every record) when you display it.

Why are applicationId / accessKey required and not provided? Because Rakuten binds API usage, rate limits, and commercial-use rules to an application ID, and that ID should be yours. They are entered as secrets and redacted from all logs.

Any privacy concerns? Product / shop / hotel data only. Review bodies, reviewer names, and phone/fax numbers are deliberately not read. Automated tests assert no phone/e-mail strings and full source attribution on every record.

Rate limits / server load? One sequential connection, ≥ 1.1 s between requests (Rakuten caps at ~1/sec per app), exponential backoff on 429/5xx, a hard per-run request budget, and no rate-limit evasion — a persistent block fails the run visibly.

Search terms this Actor answers

Rakuten API actor · Rakuten Ichiba product data · Japan e-commerce product data · Rakuten Travel data · Rakuten hotel search API · Japan online shopping price data · Rakuten Ichiba item search · Japan hotel & ryokan data · Rakuten affiliate product feed

Note for the Apify automated build test

This Actor requires a valid personal Rakuten applicationId (secret, plus accessKey on current endpoint versions) to make any live call, so Apify's default automated run test cannot pass unattended (no key). An automated-test exemption is requested for this Actor (same handling as other key-required API Actors, e.g. japan-yahoo-shopping-api, japan-radio-certifications). Functionality is covered by the unit test suite (npm test, 37 tests) over mock API fixtures for both modes; a live run needs the buyer's own application ID.

---

Official APIs: Rakuten Ichiba Item Search — https://webservice.rakuten.co.jp/documentation/ichiba-item-search ; Rakuten Travel SimpleHotelSearch — https://webservice.rakuten.co.jp/documentation/simple-hotel-search . Terms: https://webservice.rakuten.co.jp/guide/rule . Credit Supported by Rakuten Developers is embedded in every record. Unofficial; not affiliated with Rakuten Group, Inc.