POST /api/estat/releases/search
Price: 5 credits
Search the release calendar of e-Stat, the Government of Japan's statistics portal, by date range, statistics, organization and theme: each scheduled release with its date, organization, statistics code, title and detail link
Without dates the next 31 days from today (Japan time) are searched. release_date_text keeps the calendar's own wording, which names a part of the month when the exact day is not fixed.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)date_from integer nullable — Earliest release day, unix seconds, day-granular (UTC day) (examples: 1790812800)date_to integer nullable — Latest release day, unix seconds, day-granular (UTC day) (examples: 1793404800)statistics_code string nullable — Statistics code (examples: "00350300")organization string nullable — Organization code (examples: "00350")theme string nullable — Theme (major classification) (one of: "population_and_households", "labor_and_wages", "agriculture_forestry_and_fisheries", "mining_and_manufacturing", "domestic_trade_and_services", "business_household_economy", "housing_estate_and_construction", "energy_and_water", "transport_and_sightseeing", "information_communication_science_and_technology", "education_culture_sports_and_life", "administration_and_public_finance", "justice_security_and_environment", "social_security_and_sanitation", "international", "others"; examples: "business_household_economy")count integer required — Max number of results (min: 1; max: 5000)@type string (default: "EstatRelease")released_at integer nullablerelease_date_text string nullableorganization string nullablestatistics_code string nullableurl string nullable422 — date_from is after date_to, or a code is not in e-Stat's format 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 — The entity was not found, or a precondition failed 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.