/rakuten_travel/hotels/plans

POST /api/rakuten_travel/hotels/plans

Price: 10 credits

Get Rakuten Travel (楽天トラベル) accommodation plans for a hotel/ryokan by hotelNo (or hotel URL) for a given stay: each plan with its name, description, period, images and bookable room types — room type, bed type, size, meal, capacity, payment options, cancellation policy, total price, price per person and points.

How to use it

Fetch accommodation plans for a single Rakuten Travel (楽天トラベル) hotel/ryokan by numeric hotelNo (e.g. '28576') or a full hotel URL, for a specific stay (checkin/checkout dates and number of adults). Returns a list of plans, each with name, description, images and a list of room types carrying price, price_per_person, meal, capacity, bed_type, cancellation policy and remaining vacancy. Prices are date- and guest-dependent.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• hotel string required — Rakuten Travel hotel as a numeric hotelNo or a full hotel URL (examples: "28576", "https://travel.rakuten.co.jp/HOTEL/28576/28576.html"; minLength: 1)
• checkin string required — Check-in date (YYYY-MM-DD) (format: date; examples: "2026-07-15")
• checkout string required — Check-out date (YYYY-MM-DD) (format: date; examples: "2026-07-16")
• adults integer — Number of adult guests (default: 2; min: 1)
• count integer required — Max number of plans to return (min: 1)

Response

• @type string (default: "RakutenTravelHotelPlan")
• id string required
• name string required
• description string nullable
• images array (default: [])
• available_from string nullable
• available_to string nullable
• rooms array (default: [])
  • @type string (default: "RakutenTravelHotelPlanRoom")
  • id string required
  • room_type string nullable
  • bed_type string nullable
  • room_info string nullable
  • description string nullable
  • meal string nullable
  • capacity string nullable
  • payment string nullable
  • cancellation string nullable
  • price integer nullable
  • price_per_person integer nullable
  • points integer nullable
  • vacant_room_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Hotel not found (well-formed hotelNo but the hotel does not exist) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.