POST /api/yahoo/realestate/projects/search
Price: 10 credits
Search Yahoo! Real Estate Japan (Yahoo!不動産) new-build / pre-sale condo projects (新築マンション) by prefecture, optionally narrowed to a municipality, with filters: price range, exclusive floor-area range, walking distance to the nearest station, floor-plan layouts, earliest move-in timing and a rich catalogue of project themes and amenities (tower / large-scale / low-rise, on-sale vs upcoming, pets ok, seismic-isolation, delivery box, floor heating, near supermarket / park / school, and more). Returns project cards with name, price range, image, feature tags and a lead description.
Search Yahoo! Real Estate (Yahoo!不動産) new-build condo projects. Provide pref (e.g. 'tokyo'); optionally city (5-digit municipality code). Filters: price_min/price_max (JPY), include_undecided_price, area_min/area_max (m2), walk_max (minutes), layouts (upto_1ldk/two_room/three_room/four_room_plus), move_in (immediate/within_3_months/within_6_months), facets (tower/large_scale/low_rise/on_sale/upcoming_sale/pets_ok/seismic_isolation/delivery_box/floor_heating/supermarket_nearby/park_nearby/...), sort (newest/most_reviewed/station_near/price_asc/price_desc/area_asc/area_desc/most_viewed). Each result has id, url, name, price, image, tags and lead.
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 Shinjukuprice_min integer nullable — Minimum price (JPY) (min: 0)price_max integer nullable — Maximum price (JPY) (min: 0)include_undecided_price boolean — Also include projects whose price has not been announced yet (default: false)area_min number nullable — Minimum exclusive floor area (m2) (min: 0)area_max number nullable — Maximum exclusive 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: "upto_1ldk", "two_room", "three_room", "four_room_plus")move_in string nullable — Earliest move-in timing (one of: "immediate", "within_3_months", "within_6_months")facets array — Required project themes, amenities and conditions (all must match) (default: []; one of: "new_within_30_days", "has_floor_plan", "has_model_room", "actual_unit_viewable", "on_sale", "upcoming_sale", "online_service", "has_unit_layout_map", "tower", "low_rise", "large_scale", "all_units_south_facing", "eco", "quiet_residential_area", "supermarket_nearby", "park_nearby", "nursery_nearby", "elementary_school_nearby", "hospital_nearby", "all_electric", "full_parking", "pets_ok", "seismic_isolation", "resident_manager_24h", "childcare_friendly", "unit_security_system", "ene_farm", "solar_power", "flexible_reform", "multiple_train_lines", "terminal_station", "garbage_24h", "counter_kitchen", "independent_kitchen", "ih_stove", "disposer", "walk_in_closet", "shoes_in_closet", "study_room", "delivery_box", "shared_facilities", "guest_room", "full_flat_floor", "external_insulation", "floor_heating", "fiber_optic")sort string — Sort order (default: "newest"; one of: "newest", "most_reviewed", "station_near", "price_asc", "price_desc", "area_asc", "area_desc", "most_viewed")count integer required — Max number of results to return (min: 1)@type string (default: "YahooRealestateProjectCard")id string requiredurl string requiredname string nullableprice string nullableimage string nullabletags array (default: [])lead 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.