Skip to main content

nordic-balancing

Python client for Nordic electricity balancing and imbalance data, normalised to 15-minute UTC intervals.

Status: alpha. Releases are on PyPI. Every source is checked against its live API, but the API of this library may still change between 0.x versions. See CHANGELOG.md.

Install

pip install nordic-balancing            # httpx is the only dependency
pip install "nordic-balancing[pandas]"  # adds to_frame()

Python 3.12 or newer.

Why

Nordic balancing data is spread across several transmission system operators and eSett, each with its own API, authentication, time zone handling and resolution history. The Nordic markets moved to 15-minute resolution in stages (imbalance settlement in 2023, mFRR energy activation and intraday in 2025, day-ahead in October 2025), so the same series can change resolution mid-history.

nordic-balancing aims to give one typed interface over these sources, with every series in UTC on 15-minute intervals and a dated record of resolution and price-formula changes.

Usage

from datetime import UTC, datetime, timedelta

from nordic_balancing import BiddingZone, ESettClient, EnergiDataServiceClient

start = datetime(2026, 1, 15, tzinfo=UTC)
with EnergiDataServiceClient() as eds:
    prices = eds.imbalance_prices(start, start + timedelta(hours=1), [BiddingZone.DK1])

with ESettClient() as esett:
    nordic_prices = esett.imbalance_prices(start, start + timedelta(hours=1))  # all 12 zones

for p in prices:
    print(p.start, p.zone, p.imbalance_price_eur, p.dominating_direction)

With the pandas extra, to_frame turns any list of records into a DataFrame: one row per record, one column per field except raw, start in UTC, None as NaN, and directions as nullable integers.

from nordic_balancing import to_frame

frame = to_frame(nordic_prices).set_index(["start", "zone"])

Every query takes timezone-aware datetimes and returns intervals starting in [start, end), keyed by their UTC start. A price of None means the source has not published it yet or does not provide it. resolution retains the source's publication interval; historical hourly values are expanded into four quarters. raw is a read-only mapping over a deep copy of the source record, private to that record; only its top level rejects writes, so treat nested values as read-only too.

Set FINGRID_API_KEY to a free key from https://developer-data.fingrid.fi. Use with FingridClient() as fingrid: after importing it from nordic_balancing. Call fingrid.imbalance_prices(start, end) for FI prices, or series(dataset_id, start, end). series() expands hourly records only for datasets 319, 244, 106 and 369; any other dataset must be 15-minute, and an hourly record raises SourceError.

Svenska kraftnät needs no key. Call SvKClient().capacity_market(ReserveProduct.MFRR, start, end) for SE1–SE4 capacity prices and volumes.

Data contracts

Every client enforces the same contracts; a violation raises SourceError.

  • C1 Window. Queries take aware datetimes and return exactly the intervals whose start is in [start, end), at any sub-second precision of start/end.
  • C2 Pagination. Rows fetched must equal the total the source reported; a missing or invalid total, a short or empty page before the total is reached, or a mismatch is an error.
  • C3 Duplicates. Two source records for the same series key (zone and interval start, plus product and direction for SvK) are an error, even when the values are equal. ENTSO-E is the exception: an interval published under several price categories with one equal price collapses to that price, with every category kept in raw; unequal prices, or equal prices at different resolutions, raise.
  • C4 Missing vs unpublished. An interval the source did not return is absent from the result; a record returned with a null value has that field set to None. Clients never fill gaps.
  • C5 Numbers. Values must be JSON numbers (bool rejected), finite and convertible to float.
  • C6 Outside window. Records outside the requested query window are an error.
  • C7 Resolution. resolution is the source's publication interval; hourly records are repeated across four quarters. Sources can label the same price differently: ENTSO-E kept PT60M for SE and NO until 2025-03-18T00:00Z, eSett switched to 15 minutes on 2023-05-21T22:00Z (see docs/RELEASE_EVIDENCE.md).
  • C8 Transport. Network and protocol failures surface as SourceError, never as raw httpx exceptions. HTTP 429/503 are retried, then raise RateLimitError, which is raised at once when Retry-After exceeds 300 s. HTTP 502/504, timeouts and dropped connections are retried within the same max_retries budget, then raise SourceError.

reconcile_imbalance_prices reports differences between two sources; it never merges series or picks a source. Zones present in only one input are listed in primary_only_zones / reference_only_zones rather than dropped silently.

See docs/RELEASE_EVIDENCE.md for provider verification status, observed API behaviour and known limitations.

Sources

Source Client Data Access Verified against the live API
Energinet — Energi Data Service EnergiDataServiceClient DK1/DK2 imbalance prices and components, from 2025-03-04 free, no key yes
Fingrid FingridClient FI imbalance prices, mFRR up/down prices, dominating direction; any 15-minute dataset via series() free API key yes
Svenska kraftnät SvKClient SE1–SE4 mFRR and aFRR capacity market prices and volumes (hourly, expanded to 15 minutes) free (CC-BY-4.0) yes
eSett ESettClient Imbalance prices, all 12 Nordic zones, from 2021-10-31T23:00Z free, no key yes
ENTSO-E Transparency Platform EntsoeClient Imbalance prices (A85), all 12 Nordic zones, from 2021-10-31T23:00Z free token (ENTSOE_API_KEY) yes

Not covered yet: Energi Data Service mFRR/aFRR datasets, and activated balancing energy volumes. Out of scope: generic day-ahead price clients and mFRR bid submission — other projects already cover those.

Development

uv sync
uv run pytest
uv run ruff check .
uv run ruff format --check .
uv run mypy
uv run pytest -m live      # calls the real APIs; not run by default

Licence

MIT — see LICENSE. Data retrieved through this library remains subject to each source's own terms of use.

This is an independent project. It is not affiliated with, endorsed by or supported by Energinet, Fingrid, Svenska kraftnät, eSett, ENTSO-E or any other data provider.

Metadata

Release files for nordic-balancing 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nordic-balancing 0.1.0
File Size Uploaded
nordic_balancing-0.1.0.tar.gz 29.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for nordic-balancing 0.1.0
File Interpreter ABI Platform
nordic_balancing-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 67.9 kB

Release files / nordic_balancing-0.1.0.tar.gz

Download URL nordic_balancing-0.1.0.tar.gz
Size 29.3 kB
Tags Source
SHA-256 checksum
How to use checksums
96ee3600636cd6e2fda9522a96f69f63c1cfa0cb0749c3611fae9ace3e4d8abc
BLAKE2b-256 checksum
How to use checksums
4f4338f70401902a255c28e73223b60510dbb8bbcecca446f84c65c216ccb1c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.

Transparency log

Release files / nordic_balancing-0.1.0-py3-none-any.whl

Download URL nordic_balancing-0.1.0-py3-none-any.whl
Size 38.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2d68f90f7789b2b96132a9f5675dec0e2354d99cc6a2027bd927240866635e21
BLAKE2b-256 checksum
How to use checksums
3cff9bfcedaf6569d322def734d7e43f34ed9ff55b9de3dc084b38769462717a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page