/rosenka/tables

POST /api/rosenka/tables

Price: 20 credits

Get one valuation table of Japan's National Tax Agency land valuation standards (財産評価基準書) by year and prefecture: a municipality's valuation-ratio table (評価倍率表) or one of the prefecture's supplementary tables, with its PDF link, page count and, where the PDF carries a text layer, the text of each page. Most ratio tables are scanned images without a text layer; a few carry one and their page text is returned

How to use it

table=ratios takes a municipality code from rosenka/municipalities; every other table type is prefecture-wide and takes no municipality. The supplementary tables carry a text layer; the page text keeps the PDF's reading order, not its table grid.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• year integer required — Assessment year (年分) (examples: 2026, 2018; min: 2018)
• prefecture string required — Prefecture (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"; examples: "tokyo", "osaka")
• table string required — Table type (one of: "ratios", "large_factory_land", "golf_course_land", "land_development_cost", "mineral_spring_land", "miscellaneous_land", "cultivation_rights", "occupancy_rights", "rented_house_ratio", "standing_timber", "telephone_subscription_right", "agricultural_investment_price", "building_multiplier", "restricted_forest"; examples: "land_development_cost", "ratios")
• municipality string nullable — Municipality code, for the ratios table (examples: "d24204")

Response

• @type string (default: "RosenkaTable")
• id string required
• table_type string required (one of: "ratios", "large_factory_land", "golf_course_land", "land_development_cost", "mineral_spring_land", "miscellaneous_land", "cultivation_rights", "occupancy_rights", "rented_house_ratio", "standing_timber", "telephone_subscription_right", "agricultural_investment_price", "building_multiplier", "restricted_forest")
• year integer required
• prefecture string required (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")
• municipality_code string nullable
• url string required
• pdf_url string required
• page_count integer required
• has_text_layer boolean required
• pages array (default: [])
  • @type string (default: "RosenkaTablePage")
  • number integer required
  • text string required

Errors

• 422 — table=ratios without municipality, or municipality with another table type 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 table of that type for that year, prefecture and municipality 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.