Skip to main content

Data Coverage & Freshness

SENS aggregates regulated distribution tariffs from all major Polish distribution system operators (DSOs) — PGE Dystrybucja, TAURON Dystrybucja, Enea Operator, Energa-Operator, Stoen Operator, and others — directly from tariff decisions approved by URE (the Polish energy regulator). This isn't scraping, and it isn't a manually-maintained table refreshed once a quarter: every newly published tariff flows through an extraction pipeline and shows up in the API without manual intervention.

Check current coverage yourself​

The number of available records grows with every URE publication — instead of relying on a number written in this documentation (which will go stale), ask the API directly:

curl -s "https://api.getsens.energy/api/v1/tariffs?size=1" \
  -H "X-API-KEY: sens_live_your_key_here" | jq .total

The total field in the response is the real, current record count — always more current than any static description could be.

Freshness, not just coverage​

Data without a signal for when it changed is less useful than it seems — especially for clients polling the API on a schedule (aggregators, VPP operators, trading systems). That's why every record carries its own update_time, and the API supports delta queries:

curl -s "https://api.getsens.energy/api/v1/tariffs?since=2026-08-01" \
  -H "X-API-KEY: sens_live_your_key_here"

Full mechanism: Delta queries (since).

What this means for your integration​

  • You don't need to build your own URE-decision extraction pipeline — that's exactly what SENS does for you.
  • You don't need to poll the entire dataset on a schedule — since returns only what actually changed.
  • The source is always traceable — every record carries provenance back to the URE document/decision it was extracted from, which matters for audits or disputes over an applied rate.