/mlit_reinfolib/appraisal-reports

POST /api/mlit_reinfolib/appraisal-reports

Price: 5 credits

One official land price appraisal report (鑑定評価書): appraiser, appraised value and price per m², valuation, appraisal and survey dates, the land and its neighbourhood, highest and best use, the comparison, income, cost and development prices, market characteristics, the reasoning and the full report text

How to use it

Take appraisal_report_id from a public notice record of 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)
• report string required — Appraisal report id or URL (examples: "2026131010001", "https://www.reinfolib.mlit.go.jp/landPrices_/realEstateAppraisalReport/2026/13/2026131010001.html"; minLength: 1)

Response

• @type string (default: "MlitAppraisalReport")
• id string required
• url string required
• year integer required
• prefecture_code string required
• appraiser string nullable
• submitted_date integer nullable
• appraised_value number nullable
• price_per_sqm number nullable
• valuation_date integer nullable
• appraisal_date integer nullable
• survey_date integer nullable
• price_kind string nullable
• appraisal_condition string nullable
• route_price_per_sqm number nullable
• address string nullable
• land_area number nullable
• neighborhood_range string nullable
• standard_use string nullable
• standard_lot string nullable
• regional_characteristics string nullable
• regional_outlook string nullable
• highest_best_use string nullable
• comparison_price_per_sqm number nullable
• income_price_per_sqm number nullable
• cost_price_per_sqm number nullable
• development_price_per_sqm number nullable
• market_characteristics string nullable
• reasoning string nullable
• annual_change_rate number nullable
• text string 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 appraisal report 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.