/jalan/hotels/search

POST /api/jalan/hotels/search

Price: 20 credits

Search Jalan (じゃらん) hotels and ryokan by area (prefecture / large-area / small-area codes), with optional stay dates, party size, nightly budget and ordering. Returns a list of hotel cards with name, catch phrase, area, labels, lowest total and per-person price for the stay, overall rating and review count, top-rated aspects, description, access directions, photos and the number of available plans.

How to use it

Search Jalan (じゃらん) hotels/ryokan within a Japanese area. Provide prefecture (area code, e.g. '130000' for Tokyo), large_area (e.g. '137100') and optionally small_area. Optional checkin (YYYY-MM-DD), nights, adults, rooms, budget_min/budget_max (JPY per room per night) and sort (recommended / price_low / area). Each result has id (numeric hotel id), url, name, catch_phrase, region (prefecture), area, labels, is_high_class, total_price and per_person_price (JPY for the searched stay), rating, review_count, highly_rated aspects, description, access, image+images and plan_count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• prefecture string required — Jalan prefecture area code (6 digits), e.g. 130000 for Tokyo (examples: "130000")
• large_area string required — Jalan large-area code (6 digits) within the prefecture (examples: "137100")
• small_area string nullable — Optional Jalan small-area code (6 digits) to narrow within the large area (examples: "137102")
• checkin string nullable — Check-in date (YYYY-MM-DD). When omitted, the lowest available rates are returned (examples: "2026-07-10")
• nights integer — Number of nights (default: 1; min: 1)
• adults integer — Number of adults (default: 2; min: 1)
• rooms integer — Number of rooms (default: 1; min: 1)
• budget_min integer nullable — Minimum price per room per night in JPY (min: 0)
• budget_max integer nullable — Maximum price per room per night in JPY (min: 0)
• sort string — Result ordering (default: "recommended"; one of: "recommended", "price_low", "area")
• count integer required — Number of hotels to return (min: 1)

Response

• @type string (default: "JalanHotelSearchResult")
• id string required
• url string required
• name string required
• catch_phrase string nullable
• region string nullable
• area string nullable
• labels array (default: [])
• is_high_class boolean (default: false)
• total_price integer nullable
• per_person_price integer nullable
• rating number nullable
• review_count integer nullable
• highly_rated array (default: [])
• description string nullable
• access string nullable
• image string nullable
• images array (default: [])
• plan_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 — Area not found (well-formed codes but the prefecture/large-area does not exist on Jalan) 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.