Skip to main content
If you want more than a handful of operators, do not loop over /api/v1/dsos/{dso_id}/tariffs. There is a bulk endpoint, it is not paginated, and it streams.
12,910 rows for 2026 consumption tariffs, one JSON object per line.

Columns

The export contains every stage, unfiltered. That is the point of a bulk export, but it means the same tariff can appear more than once — a machine-read version and a reviewer-validated one. Deduplicate before you aggregate, or your averages will be wrong.

Deduplicating properly

Reduce to one row per tariff identity, keeping the highest stage:
Key on the tariff, not on the operator. Taking one best stage per operator drops an operator’s machine-read NE3 tariff because its NE7 tariffs happen to be validated — a mistake that is easy to make and hard to notice.

Joining to operators and geometry

The export carries vse_number. To get ElCom operator ids, names and the operators’ own source URLs:
elcom_operator_id is the join key to the GeoJSON in /api/geo/dso_areas, whose features carry operator_id.
Not every VSE-registered operator has an ElCom operator id, so not every tariff can be placed on the map. Filter on a non-null elcom_operator_id rather than assuming the join is total — 502 of 553 operators had both for 2026.

Other whole-dataset endpoints

Please cache it

The export is regenerated only when the collection pipeline runs — daily at most, and for a closed tariff year, effectively never. Pulling it hourly costs you nothing and everyone else something.
This endpoint streams and is therefore the one public read without an ETag — holding the whole dataset in memory to hash it would defeat the reason it streams. Cache it on your side by tariff year. Everywhere else, send the ETag back as If-None-Match and get a 304 with no body. See Caching and limits.