POST /api/ikyu/hotels
Price: 5 credits
Get a hotel or ryokan profile from Ikyu (一休.com): name, type, address, access, coordinates, area, check-in and check-out times, facilities and features, baths, pet and child policy, guest rating with sub-scores, Premium benefits, announcements, guide text, photos and in-house restaurants
Hotel ids come from ikyu/hotels/search. Bookable plans with prices are ikyu/hotels/plans and guest reviews are ikyu/hotels/reviews.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)hotel string required — Ikyu hotel id or hotel URL (examples: "00001278", "https://www.ikyu.com/00001278/"; minLength: 1)@type string (default: "IkyuHotel")id string requiredurl string requiredname string nullableproperty_type string nullablecatchphrase string nullableaccess string nullableaddress string nullableprefecture string nullablepostal_code string nullablephone string nullablelatitude number nullablelongitude number nullableregion object nullable@type string (default: "IkyuArea")id string requiredname string nullablearea object nullable@type string (default: "IkyuArea")id string requiredname string nullablesub_area object nullable@type string (default: "IkyuArea")id string requiredname string nullablehot_spring_area string nullableroom_count integer nullablecheck_in_from string nullablecheck_in_until string nullablecheck_out string nullableopened_date integer nullablepets_allowed boolean nullablepets_note string nullablechildren_allowed boolean nullablechildren_note string nullablehas_spa boolean nullablenotes string nullablebaths array (default: [])@type string (default: "IkyuBath")code string nullablename string nullablehot_spring_source string nullablefitness object nullable@type string (default: "IkyuFitness")opens_at string nullablecloses_at string nullablelast_admission string nullableguest_price integer nullablevisitor_price integer nullablefeatures array (default: [])@type string (default: "IkyuHotelFeature")code string requiredname string nullableavailable boolean nullableis_premium boolean nullableis_ikyu_plus boolean nullablepremium_since_date integer nullablepremium_benefits array (default: [])@type string (default: "IkyuPremiumBenefit")content string requirednote string nullablerating object nullable@type string (default: "IkyuHotelRating")average number nullablecount integer nullablesatisfaction number nullableroom number nullableservice number nullablebath number nullablefacilities number nullablemeal number nullablearea_rank integer nullablearea_rank_label string nullableannouncements array (default: [])@type string (default: "IkyuHotelAnnouncement")text string nullableimage object nullable@type string (default: "IkyuImage")url string requiredcaption string nullablecategory string nullableguide array (default: [])@type string (default: "IkyuHotelGuideSection")text string nullableimages array (default: [])@type string (default: "IkyuImage")url string requiredcaption string nullablecategory string nullablephotos array (default: [])@type string (default: "IkyuImage")url string requiredcaption string nullablecategory string nullablerestaurants array (default: [])@type string (default: "IkyuHotelRestaurant")id string requiredurl string requiredname string nullablegenre string nullablecuisine string nullableimage string nullablethemes array (default: [])@type string (default: "IkyuTheme")id string requiredname string nullablesuggested_questions array (default: [])422 — hotel is not an Ikyu hotel id or URL 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 — No Ikyu hotel under that id 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.