Glossary

Eurostat dissemination API

The Eurostat dissemination API is the keyless JSON query interface returning label, dimension category indexes/labels, a size vector and a flat value map keyed by linear position. Note the INDIC dimension is now named indic_bt - using indic triggers INVALID_QUERY_DIMENSION errors.

What is Eurostat dissemination API?

The dissemination statistics API serves one dataset per URL path - the cataloged example is /api/dissemination/statistics/1.0/data/sts_trtu_m - and answers a GET with compact JSON. The response carries the label, dimension category indexes and labels, a size vector, and a flat value map keyed by linear position, so clients reconstruct cells arithmetically rather than parsing nested structures.

A verified call used format=JSON, geo=EU27_2020, nace_r2=G47, indic_bt=NETTUR, s_adj=NSA, unit=I21 and sinceTimePeriod=2026-01 - no key, no registration. Two operational traps matter: the INDIC dimension is now named indic_bt, so legacy indic parameters fail with INVALID_QUERY_DIMENSION errors, and the databrowser UI renders nothing to plain fetchers, which makes this API the practical programmatic route.

Why does Eurostat dissemination API matter when choosing a dataset?

An API that changes dimension names mid-life breaks pipelines silently - a cached failure page looks like an empty series. Knowing the current parameter set is worth more than any SDK.

  • Dimension renames invalidate stored URLs. Requests still sending indic get INVALID_QUERY_DIMENSION errors - migrate every stored URL to indic_bt, starting with the verified sts_trtu_m pattern whose sinceTimePeriod was 2026-01.
  • Keyless access simplifies deployment. No credentials means nothing to rotate or leak, and a verified call needs only query parameters.
  • Scraping the UI is the wrong path. The databrowser renders nothing to plain fetchers, so teams that cannot use the API end up maintaining brittle scrapes for data one GET away.

How do you evaluate Eurostat dissemination API in a data source?

  1. Validate your dimension names against today's schema. INDIC became indic_bt in the cataloged evidence; run one probe call per dataset and treat INVALID_QUERY_DIMENSION as a rename signal.
  1. Reconstruct cells from the size vector deliberately. Values arrive as a flat map keyed by linear position - unit-test your index math against a known label-value pair before trusting outputs.
  1. Pin filters explicitly in every call. The verified pattern used geo=EU27_2020, nace_r2=G47, indic_bt=NETTUR, s_adj=NSA, unit=I21, sinceTimePeriod=2026-01; implicit defaults drift.
  1. Confirm the no-key path persists. Anonymous queries worked in the cataloging session; re-check periodically since authentication requirements can appear without notice.
  1. Do not scrape the browser UI as a fallback. The databrowser renders nothing to plain fetchers, so a scrape adds fragility while the API remains the supported route.

Entries that sit next to Eurostat dissemination API in this glossary:

Frequently asked questions

Does the Eurostat dissemination API require an integration key?

No. The cataloged evidence shows a verified call using only query parameters - format=JSON, geo=EU27_2020, nace_r2=G47, indic_bt=NETTUR, s_adj=NSA, unit=I21, sinceTimePeriod=2026-01 - with no registration or key.

Why does my Eurostat query return INVALID_QUERY_DIMENSION?

Most often because the dimension is named with its old label. The INDIC dimension is now indic_bt, and calls still using indic trigger INVALID_QUERY_DIMENSION errors - update the parameter name.

What shape does the dissemination API response take?

JSON containing the label, dimension category indexes and labels, a size vector, and a flat value map keyed by linear position, which clients expand into cells using the dimension order.

Datasets containing this field

Datasets containing Eurostat dissemination API

6 datasets carry eurostat dissemination api in the catalog. Open one, count the fields, judge for yourself.

Industries United States · Varies per record

Data.gov - Food-Tagged structured datasets Collection

Other Specialty Retail United States and Canada primary depth… · Continuously maintained…

Nutritionix Natural Language & Grocery API

Other Specialty Retail

Data.gov Retail Catalog (552k+ Datasets Federated Search)

title · description · publisher.name …+8 more

Industries

Edamam Food Database API

Industries 245+ countries and territories across… · 1961 to the most recent year…

FAOSTAT Food and Agriculture Statistics

Area Code / Area Code (M49) / Area · Item Code / Item Code (CPC) / Item · Element Code / Element …+5 more

Every listing shows the field dictionary, sample rows, and coverage before you commit. API, files, or your warehouse. Daily, weekly, or hourly.

Get sample rows