# /mlit_reinfolib/land-prices/search `POST /api/mlit_reinfolib/land-prices/search` Price: 5 credits Japanese official land prices — public notice (地価公示) and prefectural survey (都道府県地価調査) points — from the MLIT Real Estate Information Library: price per m² with the previous year's and the change, lot number, address, land area and shape, current use, building, roads, utilities, nearest station, zoning and regulations, coordinates and the appraisal report link ## How to use it Each record is one point in one year; pass point_id and price_type to mlit_reinfolib/land-prices for the point's every year, and appraisal_report_id to mlit_reinfolib/appraisal-reports. ## Parameters - `access-token` (string, required) ## Request body - `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500) - `count` (integer, required) — Max number of results (min: 1; max: 5000) - `price_types` (array, nullable) — Public notice prices, prefectural survey prices, or both (one of: "public_notice", "prefectural_survey"; examples: ["public_notice"]) - `year_from` (integer, nullable) — Earliest price year (examples: 2020; min: 1970) - `year_to` (integer, nullable) — Latest price year (examples: 2026; min: 1970) - `prefecture_code` (string, nullable) — Two-digit prefecture code (examples: "13") - `city_codes` (array, nullable) — Five-digit municipality codes (examples: ["13101"]; maxItems: 10) - `land_use_categories` (array, nullable) — Land use categories (one of: "residential", "future_residential", "commercial", "quasi_industrial", "industrial", "residential_in_urbanization_control", "forest_in_urbanization_control", "forest"; examples: ["commercial"]) - `lot_number` (string, nullable) — Standard or base lot number (examples: "千代田-1", "千代田5-1"; minLength: 1) - `price_min` (integer, nullable) — Lowest price per m², yen (examples: 1000000; min: 0) - `price_max` (integer, nullable) — Highest price per m², yen (examples: 5000000; min: 0) - `land_area_min` (integer, nullable) — Smallest land area, m² (examples: 100; min: 0) - `land_area_max` (integer, nullable) — Largest land area, m² (examples: 500; min: 0) - `sort_by` (string, nullable) — Sort column (one of: "price", "land_area"; examples: "price") - `sort_order` (string) — Sort direction (default: "asc"; one of: "asc", "desc"; examples: "desc") ## Response ### 200 — Successful Response - `@type` (string) (default: "MlitLandPrice") - `id` (string, required) - `point_id` (string, required) - `price_type` (string, required) (one of: "public_notice", "prefectural_survey") - `year` (integer, required) - `valuation_date` (integer, nullable) - `lot_number` (string, nullable) - `serial_number` (string, nullable) - `prefecture_code` (string, nullable) - `prefecture` (string, nullable) - `city_code` (string, nullable) - `city_county` (string, nullable) - `ward_town_village` (string, nullable) - `place_name` (string, nullable) - `lot_address` (string, nullable) - `address` (string, nullable) - `land_use_category_code` (string, nullable) - `land_use_category` (string, nullable) - `price_per_sqm` (number, nullable) - `previous_price_per_sqm` (number, nullable) - `change_rate` (number, nullable) - `land_area` (number, nullable) - `shape_code` (string, nullable) - `shape` (string, nullable) - `frontage_ratio` (number, nullable) - `depth_ratio` (number, nullable) - `utilization_code` (string, nullable) - `utilization` (string, nullable) - `current_use` (string, nullable) - `building_structure_code` (string, nullable) - `building_structure` (string, nullable) - `floors_above_ground` (integer, nullable) - `floors_below_ground` (integer, nullable) - `front_road_code` (string, nullable) - `front_road` (string, nullable) - `front_road_direction_code` (string, nullable) - `front_road_direction` (string, nullable) - `front_road_width` (number, nullable) - `front_road_station_plaza_code` (string, nullable) - `front_road_station_plaza` (string, nullable) - `front_road_pavement_code` (string, nullable) - `front_road_pavement` (string, nullable) - `side_road_code` (string, nullable) - `side_road` (string, nullable) - `side_road_direction_code` (string, nullable) - `side_road_direction` (string, nullable) - `has_gas` (boolean, nullable) - `has_water` (boolean, nullable) - `has_sewer` (boolean, nullable) - `station` (string, nullable) - `station_proximity_code` (string, nullable) - `station_proximity` (string, nullable) - `station_distance_m` (number, nullable) - `surroundings` (string, nullable) - `planning_area_code` (string, nullable) - `planning_area` (string, nullable) - `zoning_code` (string, nullable) - `zoning` (string, nullable) - `height_district_code` (string, nullable) - `height_district` (string, nullable) - `fire_zone_code` (string, nullable) - `fire_zone` (string, nullable) - `building_coverage_ratio` (number, nullable) - `floor_area_ratio` (number, nullable) - `forest_law_code` (string, nullable) - `forest_law` (string, nullable) - `park_law_code` (string, nullable) - `park_law` (string, nullable) - `common_point_type` (string, nullable) - `is_paused` (boolean, nullable) - `appraisal_report_id` (string, nullable) - `appraisal_report_url` (string, nullable) - `latitude` (number, nullable) - `longitude` (number, nullable) ## Errors ### 422 — Validation Error The request body did not validate What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause. - `detail` (array) - `loc` (array, required) - `msg` (string, required) - `type` (string, required) - `input` (any) - `ctx` (object) ### 408 The request ran past its time limit What to do: 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 What to do: 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 What to do: 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 What to do: 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 What to do: Wait at least 30 seconds, then retry. ## Response envelope Success: Array of objects (may be empty if no results) Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code. Every response carries these 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.