/eurostat/datasets

POST /api/eurostat/datasets

Price: 1 credit

Get observations from a Eurostat dataset by its code, sliced by dimension filters

How to use it

Fetch numeric observations from a single Eurostat statistical dataset by its code (e.g. nama_10_gdp for GDP, prc_hicp_midx for inflation, demo_pjan for population). Each observation is returned as a flat record with the resolved code and human label for every dimension (geography, unit, indicator, frequency, etc.), the numeric value, and an optional data-quality status flag. Use the geo, time, since, until, and filters arguments to slice the dataset to the cells you need — an unfiltered dataset can contain millions of cells. Look up the available dimension codes for a dataset via the dimensions endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• dataset string required — Dataset code (examples: "nama_10_gdp", "prc_hicp_midx", "demo_pjan")
• count integer required — Number of observations to return (min: 1)
• geo array nullable — Filter by geopolitical entity code(s) (examples: ["DE","FR","EU27_2020"])
• time array nullable — Filter by exact time period(s) (examples: ["2022","2023"])
• since string nullable — Earliest time period, inclusive (examples: "2020")
• until string nullable — Latest time period, inclusive (examples: "2024")
• filters object nullable — Additional dimension filters as a mapping of dimension code to allowed value codes (examples: {"na_item":["B1GQ"],"unit":["CP_MEUR"]})
  • * array

Response

• @type string (default: "EurostatObservation")
• dimensions array required
  • @type string (default: "EurostatObservationDimension")
  • id string required
  • code string required
  • label string nullable
• value union required
• status string nullable
• status_label 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 — Dataset not found or no observations for the requested slice 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.