POST /api/yahoo/realestate/listings/search
Price: 20 credits
Search Yahoo! Real Estate Japan (Yahoo!不動産) rental listings by prefecture, optionally narrowed to a municipality, with filters: rent range, floor-area range, walking distance to the nearest station, floor-plan layouts, building types, building structures, maximum building age, an extensive amenity catalogue (separate bath/toilet, auto-lock, pets, floor heating, delivery box, elevator, corner room, south-facing, ...), rent-cost conditions (management fee included, no deposit, no key money), online support options, information-published recency, a free-text keyword and sort order. Returns listing cards with building name/type, address, nearest stations, age, floor, rent, management fee, deposit, key money, layout, area and image.
Search Yahoo! Real Estate (Yahoo!不動産) rental listings. Provide pref (e.g. 'tokyo', 'osaka', 'kanagawa'); optionally city (5-digit municipality code, e.g. '13104' Shinjuku). Filters: rent_min/rent_max (JPY), area_min/area_max (m2), walk_max (minutes), layouts (one_room/1k/1dk/1ldk/.../5k_plus), building_types (mansion/house/apartment), structures (reinforced_concrete/steel/wood/block_other), max_age (new/within_2_years/.../within_20_years), facets (separate_bath_toilet/auto_lock/pets_ok/floor_heating/delivery_box/elevator/corner_room/south_facing/...), rent_conditions (management_fee_included/no_deposit/no_key_money), online (video_call/online_viewing/it_explanation), info_open (today/within_3_days/...), keyword, sort (newest/price_incl_asc/price_incl_desc/price_asc/price_desc/area_desc/station_near/age_newest/most_viewed). Each result has id, url, building_name, building_type, stations, address, age, total_floors, structure, floor, rent, management_fee, deposit, key_money, layout, area and image.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)pref string required — Prefecture to search in (one of: "hokkaido", "aomori", "iwate", "miyagi", "akita", "yamagata", "fukushima", "ibaraki", "tochigi", "gunma", "saitama", "chiba", "tokyo", "kanagawa", "niigata", "toyama", "ishikawa", "fukui", "yamanashi", "nagano", "gifu", "shizuoka", "aichi", "mie", "shiga", "kyoto", "osaka", "hyogo", "nara", "wakayama", "tottori", "shimane", "okayama", "hiroshima", "yamaguchi", "tokushima", "kagawa", "ehime", "kochi", "fukuoka", "saga", "nagasaki", "kumamoto", "oita", "miyazaki", "kagoshima", "okinawa")city string nullable — 5-digit municipality (JIS) code to narrow the search, e.g. '13104' for Shinjukurent_min integer nullable — Minimum monthly rent (JPY) (min: 0)rent_max integer nullable — Maximum monthly rent (JPY) (min: 0)area_min number nullable — Minimum floor area (m2) (min: 0)area_max number nullable — Maximum floor area (m2) (min: 0)walk_max integer nullable — Maximum walking minutes to the nearest station (min: 1)layouts array — Floor-plan layouts to include (default: []; one of: "one_room", "1k", "1dk", "1ldk", "2k", "2dk", "2ldk", "3k", "3dk", "3ldk", "4k", "4dk", "4ldk", "5k_plus")building_types array — Building types to include (default: []; one of: "mansion", "house", "apartment")structures array — Building structures to include (default: []; one of: "reinforced_concrete", "steel", "wood", "block_other")max_age string nullable — Maximum building age (one of: "new", "within_2_years", "within_5_years", "within_10_years", "within_15_years", "within_20_years")facets array — Required amenities and conditions (all must match) (default: []; one of: "air_conditioner", "auto_lock", "two_plus_balconies", "bicycle_parking", "bathroom_dryer", "bed", "barrier_free", "bs_antenna", "separate_bath_toilet", "counter_kitchen", "closet", "parking", "satellite_broadcast", "cable_tv", "delivery_box", "elevator", "first_floor", "floor_heating", "flooring", "free_rent", "garage", "gas_stove_ok", "reheating_bath", "ih_stove", "immediate_move_in", "card_key", "lighting", "loft", "women_only", "maisonette", "instruments_ok", "resident_manager", "video_intercom", "south_facing", "elderly_welcome", "two_plus_parking", "pets_ok", "propane_gas", "roof_balcony", "corner_room", "refrigerator", "security_24h", "second_floor_or_higher", "system_kitchen", "condo_type", "students_only", "specified_quality_rental", "storage", "top_floor", "city_gas", "terrace_garden", "two_person_ok", "exclude_fixed_term", "trunk_room", "veranda", "walk_in_closet", "washlet", "washer_space", "washstand")rent_conditions array — Rent-cost conditions (management fee included, no deposit, no key money) (default: []; one of: "management_fee_included", "no_deposit", "no_key_money")online array — Online support options (video call, online viewing, IT contract explanation) (default: []; one of: "video_call", "online_viewing", "it_explanation")info_open string nullable — Only listings published within (one of: "today", "within_3_days", "within_5_days", "within_7_days")keyword string nullable — Free-text keyword (station, area or building name)sort string — Sort order (default: "newest"; one of: "newest", "price_incl_asc", "price_incl_desc", "price_asc", "price_desc", "area_desc", "station_near", "age_newest", "most_viewed")count integer required — Max number of results to return (min: 1)@type string (default: "YahooRealestateListingCard")id string requiredurl string requiredstructure_id string nullablebuilding_name string nullablebuilding_type string nullablestations array (default: [])@type string (default: "YahooRealestateStation")line string nullablestation string nullablewalk_min integer nullableaddress string nullableage string nullabletotal_floors string nullablestructure string nullablefloor string nullablerent integer nullablemanagement_fee integer nullabledeposit string nullablekey_money string nullablelayout string nullablearea number nullableimage string nullable422 — 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 — The entity was not found, or a precondition failed 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.