Eurostat

byAPI3·Free·Airnode v0.1.4

Eurostat is the statistical office of the European Union, and its dissemination API is where the official European figures come from: national accounts, prices, employment, energy, trade, demographics and several thousand other datasets, on the same release calendar the published statistics follow. This Airnode wraps it, so a consumer receives what Eurostat published with a signature saying this Airnode read it then, which matters on a source that revises: a figure carries a p or an e flag while it is provisional or estimated, and the final number arrives later.

A dataset is addressed by its code, such as nama_10_gdp for GDP, and is a cube: several dimensions, one of which is always time, with an observation at each combination that has one. Answers are JSON-stat, which is that cube flattened, so a value is found by its position rather than by a key. Describing a dataset first is how a caller learns which dimensions it has and what they are called.

Reuse terms. Eurostat authorises reuse, commercial reuse included, without a written licence, on condition that the source is cited. The citation Eurostat asks for is the dataset's DOI and the date it was accessed, and the DOI travels in every response, under extension.annotation as DISSEMINATION_DOI_XML. Three things are outside that permission and are the consumer's to check rather than this Airnode's to filter: data whose copyright the dataset identifies as belonging to a third party, data supplied by non-EU and non-EFTA countries, and certain trade data, for which commercial reuse is not granted. Where reuse involves modifying the figures, that has to be stated to whoever receives them.

Every response carries an EIP-191 signature from the Airnode that served it, so the data can be attributed back to its source rather than trusted on reputation.

Interface

Served at https://airnode-eurostat.fly.dev/. Each operation is reached the way the provider documents it, under https://airnode-eurostat.fly.dev/api, and answers with the provider's own response and the attestation in headers, so a client built against the provider works unchanged. The same operations are also served as one JSON envelope on POST /, which the HTTP interface covers. Every request below can be sent from this page, and what comes back is verified right here in the browser.