/mlit_reinfolib/land-prices

POST /api/mlit_reinfolib/land-prices

Price: 5 credits

Every year of one official land price point (public notice or prefectural survey), newest first: price per m² with the previous year's and the change, lot number, address, land, building, roads, utilities, nearest station, zoning and regulations, coordinates and the appraisal report link

How to use it

Take point_id and price_type from mlit_reinfolib/land-prices/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• point_id string required — Land price point id (examples: "3008945", "12007363"; minLength: 1)
• price_type string required — Public notice or prefectural survey point (one of: "public_notice", "prefectural_survey"; examples: "public_notice")

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 — 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 — No land price point of that type 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.

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.