v1
latestOpenAPI 3.1.02026-07-2694207444.7 KBYearly Scheduled Physical Flows
Scheduled physical flows are published for the day-ahead market after the Nordic Flow-based go-live on the 30th of October 2024.
Scheduled physical flows are re-calculated flows for Nordic flow-based regions. The Nordic Flow-based implementation sometimes ends up breaching physical constraints in the power grid, and a post-coupling re-calculation is done and published to the JAO publication tool, which is the source of this data.
The re-calculated flows should end up with every area having the same net position (+/- ~0.1MW) as the original flows coming from Euphemia, but internal flows inside the regions might be re-routed.
Scheduled physical flows are the basis of what capacities are later released to intraday auctions as well as the intraday market. The need to re-calculate flows coming from Euphemia only exist in the Nordic flow-based regions.
This endpoint returns all scheduled physical flows for a year and area.
Response field descriptions
dailySummaries: contains a list of daily summaries for all flows for that day
- totalImport: total import volume for the day, in MWh
- totalExport: total export volume for the day, in MWh
- totalNetPosition: total net position for the day (total import - total export), in MWh
- connectionSummaries: list of all connections used for the day, with total imports and exports given in MWh
flows: a list of delivery periods, containing all flows for that period
- byConnection: a list of all connections that has a flow for the period. Each connection is identified by an area and optionally by a connection name. The Connection name is only present if multiple connections exists on the same border. import gives the import volume in MW, export the export volume in MW and netPosition describes import-export
- totalImport: sum of all connection import volumes given in MW
- totalExport: sum of all connection export volumes given in MW
- totalNetPosition: total import - total export
Query parameters
One area. For example NO1. Supported: DK1,DK2,FI,NO1,NO2,NO3,NO4,NO5,SE1,SE2,SE3,SE4
Year in CET (format: yyyy, e.g., 2024)
Response
OK