POST /api/estat/tables
Price: 20 credits
Get one statistical table of e-Stat, the Government of Japan's statistics portal, by table ID: title, statistics, dataset category, theme, publisher and contacts, publication date, cell count, and every dimension of the table with all of its item codes, names, hierarchy levels and units
Table IDs come from estat/tables/search. Dimension ids and item codes are the keys of the filters parameter of estat/observations/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)table string required — Statistical table ID or DB view URL (examples: "0003427113", "https://www.e-stat.go.jp/en/dbview?sid=0003427113")@type string (default: "EstatTable")id string requiredurl string requiredtable_number string nullableoverview string nullablestatistics_code string nullablestatistics_name string nullabledataset_categories array (default: [])@type string (default: "EstatDatasetCategory")id string nullablename string requiredtheme string nullabletheme_code string nullablesub_theme string nullablesub_theme_code string nullableorganization string nullableorganization_code string nullableemail string nullablephone string nullablestatistics_url string nullablestatistical_type string nullablesurvey_period string nullablefrequency string nullabletabulation_areas array (default: [])table_categories array (default: [])cell_count integer nullablepublished_at integer nullabledimensions array (default: [])@type string (default: "EstatDimension")id string requiredname string requiredkind string nullabledimension_type string nullableposition string requireditem_count integer requiredmembers array (default: [])@type string (default: "EstatDimensionItem")code string requiredname string requiredlevel string nullableparent_code string nullableunit string nullableexplanation string nullable422 — table is not a 10-digit table ID or DB view URL 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 statistical table 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.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.