openapi: 3.0.3
info:
title: Nord Pool Data Portal API (Public) Auction API
version: '1.0'
description: The unauthenticated JSON API behind the Nord Pool Data Portal (data.nordpoolgroup.com), where Nord Pool publishes day-ahead electricity prices for the Nordic, Baltic, CWE, and UK bidding areas. These endpoints return the same day-ahead auction results shown on the public website, in 15-minute Market Time Unit resolution, and are widely used by open-source integrations such as Home Assistant. IMPORTANT - this API is not part of Nord Pool's officially documented, subscription-backed developer offering. It is not covered by an SLA or the API General Terms, and Nord Pool may change or restrict it at any time. The two operations below were observed live and verified returning data on 2026-07-11; request and response shapes are modeled from those observed responses rather than from official reference documentation. For supported programmatic access, use the Nord Pool Market Data API (data-api.nordpoolgroup.com) with a Power Data Services subscription.
contact:
name: Nord Pool
url: https://data.nordpoolgroup.com/
servers:
- url: https://dataportal-api.nordpoolgroup.com
description: Nord Pool Data Portal backend (public, unauthenticated)
tags:
- name: Auction
paths:
/api/v2/Auction/{market}/BidCurves/ByRegion:
get:
tags:
- Auction
summary: Aggregated bidding curves
description: "Returns aggregated bid curves for a date and region.\n \nAggregated bidding curves explains why the price forms as it does in a region for a market. If we plot aggregated supply and demand curves in the same chart, then the intersection of these two curves should happen on the realized price point.\n \nSome regions contain multiple delivery areas. In this case, the intersection point will explain what the price would have been if no capacity constraint existed in between the sub-areas. Usually regions consisting of multiple delivery areas are aggregated if the amount of trading activity in the sub-areas is small enough that it would reveal the trading strategy of the few traders active in the area. \n \nThis endpoint returns aggregated bidding curve data for each delivery period for the queried CET date. \n\n### Response field descriptions\n\n#### aggregatedOrderPositions\n- **exportVolume**: volume exported from the region and period\n- **importVolume**: volume imported to the region and period\n- **realizedCurveDemandVolume**: volume of activated demand curve orders for the region, period, and resolution\n- **realizedCurveSupplyVolume**: volume of activated sell curve orders for the region, period, and resolution\n- **realizedNonCurveDemandVolume**: volume of activated buy blocks for the region, period, and resolution\n- **realizedNonCurveSupplyVolume**: volume of activated sell blocks for the region, period, and resolution\n- **demandCurve**: list of aggregated demand (=buy) curve order volume for price points\n- **supplyCurve**: list of aggregated supply (=sell) curve order volume for price points\n- **aggregatedDemandCurve**: list of aggregated demand price points. Consist of adjusted demand curve plus net export if net export > 0, plus realized non curve demand volume for the resolution as well as demand curve volume and demand non curve volume from other resolutions. Only generated for the smallest resolution period\n- **aggregatedSupplyCurve**: list of aggregated supply price points. Consist of adjusted supply curve plus net import if net import > 0, plus realized non curve supply volume for the resolution as well as supply curve volume and supply non curve volume from other resolutions. Only generated for the smallest resolution period\n \n#### blockOrders\n- **side**: Buy or Sell\n- **exclusiveGroupId**: if not null, then this block is part of an exclusive group. Group all blocks by exclusive group id to see the exclusive group.\n- **minimumAcceptanceRatio**: the minimum acceptance ratio needed for the block to activate. Typically in the 0.5-1 range, where 0.5 = 50% of the volume needs to be filled to activate\n- **linkedOrderId**: if not null, then this block will only activate if the linked block order with this id activates. To find the parent, find the block order with the corresponding id.\n- **price**: the average price for the block order to activate\n- **paradoxicallyRejected**: if true, then the block restrictions are within the correct price and volume limits, but activating the block would cause price and volume to shift enough to disqualify the block from activation.\n- **actualAcceptanceRatio**: the ratio of the block that was accepted, in a range of 0 - 1. 1 = 100% of volume accepted.\n- **intervals**: periods for the block, with corresponding volumes and accepted volumes."
externalDocs:
description: Data portal link
url: https://data.nordpoolgroup.com/auction/day-ahead/aggregated-bid-curves?deliveryDate=latest&bidCurveArea=SE
parameters:
- name: market
in: path
required: true
schema:
$ref: '#/components/schemas/AggregatedBidCurveMarkets'
- name: region
in: query
required: true
schema:
$ref: '#/components/schemas/ClusterType'
- name: date
in: query
description: Delivery date, referring to CET date. Format yyyy-MM-dd, for example 2024-08-15
required: true
schema:
type: string
format: date
responses:
'200':
description: OK
content:
text/plain:
schema:
$ref: '#/components/schemas/ApiAggregatedCluster'
application/json:
schema:
$ref: '#/components/schemas/ApiAggregatedCluster'
text/json:
schema:
$ref: '#/components/schemas/ApiAggregatedCluster'
'401':
description: Unauthorized
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'403':
description: Forbidden
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'400':
description: Bad Request
content:
text/plain:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
application/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
text/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
/api/v2/Auction/Capacities/ByAreas:
get:
tags:
- Auction
summary: ATC Capacities
description: "ATC capacities constrains how much power can flow in between two areas. The matching algorithm takes these capacities into account when optimizing power flow from low price to high price areas. Note that for some regions in some markets, flow based capacity constraints are used instead or in combination with ATC capacities.\n \nCapacities are given for each delivery period for the delivery date in question, and are separated into import and export capacities.\n \n### Response field descriptions\n \n**importsByConnection**\n- **area**: the area imported from\n- **connection**: the named connection to the import area. In some cases, multiple capacity values exist in between two areas - if that's the case, then connection will be used to distinguish the values.\n- **capacity**: the max MW that can be imported on this connection\n- **lossFactor**: in case there is a loss on the cable, then the loss factor tells how much power will be lost. Given a loss factor of 0.02 then 2% of the power gets lost in transit. If we put in 100 MW on the exporting side then 98MW arrives in the import area. \n- **rampingRestriction**: some connections can't change the power flow too quickly. In these cases, a ramping restriction will be present. Ramping restrictions are given in MW, telling how much capacity can change from the previous period. If we have a ramping value of 100 MW, then going from delivery period 01:00 to 02:00, then the flow value can only change +/- the ramping value from the previous period.\n- **alreadyAllocatedCapacity**: capacity which is already in use. If ramping restrictions exist, then the already allocated capacity needs to be taken into account. This is mostly relevant for intraday auctions where there is planned flows already in place.\n \n**exportsByConnection**\n- **area**: the area exported to\n- **connection**: the named connection to the export area. In some cases, multiple capacity values exist in between two areas - if that's the case, then connection will be used to distinguish the values.\n- **capacity**: the max MW that can be exported on this connection\n- **lossFactor**: in case there is a loss on the cable, then the loss factor tells how much power will be lost. Given a loss factor of 0.02 then 2% of the power gets lost in transit. If we put in 100 MW on the exporting side then 98MW arrives in the import area. \n- **rampingRestriction**: some connections can't change the power flow too quickly. In these cases, a ramping restriction will be present. Ramping restrictions are given in MW, telling how much capacity can change from the previous period. If we have a ramping value of 100 MW, then going from delivery period 01:00 to 02:00, then the flow value can only change +/- the ramping value from the previous period.\n- **alreadyAllocatedCapacity**: capacity which is already in use. If ramping restrictions exist, then the already allocated capacity needs to be taken into account. This is mostly relevant for intraday auctions where there is planned flows already in place.\n \n**importGroupRestriction**\n- **areas**: the areas affected by this restriction\n- **capacity**: the total import capacity that is possible when summing together all area capacities. This is generally larger than a single area capacity, but smaller than the sum of areas.\n\n**exportGroupRestriction**\n- **areas**: the areas affected by this restriction\n- **capacity**: the total import capacity that is possible when summing together all area capacities. This is generally larger than a single area capacity, but smaller than the sum of areas.\n\n**externalImportConstraint**: external import constraints limit the bidding zone net position which represents the total net exchange of the BZ with its neighbors both in FlowBased and ATC network models. The net position is defined as sum \\(export flow\\) - sum \\(import flow\\), and must be higher or equal to -\\(external import constraint\\).\n \n**externalExportConstraint**: external export constraints limit the bidding zone net position which represents the total net exchange of the BZ with its neighbors both in FlowBased and ATC network models. The net position is defined as sum \\(export flow\\) - sum \\(import flow\\), and must be less or equal to \\(external export constraint\\).\n \n**totalImport**: the total available import capacity, taking into account import group restrictions if any exist.\n \n**totalExport**: the total available export capacity, taking into account export group restrictions if any exist.\n \n**maxNtcValues**: a list of the maximum capacity value possible for certain connections. \n- **areaFrom**: area which electricity is flowing from\n- **areaTo**: area which electricity is flowing to \n- **connection**: name of connection, if multiple connections exists in between two areas\n- **maxNtc**: the net transfer capacity max value for this connection"
externalDocs:
description: Data portal link
url: https://data.nordpoolgroup.com/auction/day-ahead/capacities?deliveryDate=latest&deliveryArea=EE
parameters:
- name: market
in: query
required: true
schema:
$ref: '#/components/schemas/AuctionCapacityMarkets'
- name: areas
in: query
description: "Comma-separated list of areas (e.g., NO1, NO2). \n\nSupported: SE(legacy), NO1, NO1A, NO2, NO2_ND, NO2_NK, NO2_SK, NO2A, NO3, NO4, NO5, SE1, SE2, SE3, SE3_FS, SE3_KS, SE3_SWL, SE4, SE4_BC, SE4_NB, SE4_SP, SE4_SWL,\nFI, FI_EL, FI_FS, DK1, DK1_CO, DK1_DE, DK1_KS, DK1_SB, DK1_SK, DK1A, DK2, DK2_KO, DK2_SB, EE, LT, LV, AT, BE, DE_BC, DE_DK1, DE_KO, DE_NK, FR, GER, NL,\nNL_CO, NL_ND, PL, PL_LP, PL_SP, TEL, BG, RO_BG, UK"
required: true
schema:
minItems: 1
type: string
items:
type: string
- name: date
in: query
description: Delivery date, referring to CET date. Format yyyy-MM-dd, for example 2024-08-15
required: true
schema:
type: string
format: date
responses:
'200':
description: OK
content:
text/plain:
schema:
type: array
items:
$ref: '#/components/schemas/ApiAuctionCapacity'
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ApiAuctionCapacity'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/ApiAuctionCapacity'
'401':
description: Unauthorized
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'403':
description: Forbidden
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'400':
description: Bad Request
content:
text/plain:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
application/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
text/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
/api/v2/Auction/Capacities/Yearly/ByArea:
get:
tags:
- Auction
summary: Yearly ATC capacities
description: "Returns a list of auction capacities for a market, year and one area.\n \n### Response field descriptions\n \n**importsByConnection**\n- **area**: the area imported from\n- **connection**: the named connection to the import area. In some cases, multiple capacity values exist in between two areas - if that's the case, then connection will be used to distinguish the values.\n- **capacity**: the max MW that can be imported on this connection\n- **lossFactor**: in case there is a loss on the cable, then the loss factor tells how much power will be lost. Given a loss factor of 0.02 then 2% of the power gets lost in transit. If we put in 100 MW on the exporting side then 98MW arrives in the import area. \n- **rampingRestriction**: some connections can't change the power flow too quickly. In these cases, a ramping restriction will be present. Ramping restrictions are given in MW, telling how much capacity can change from the previous period. If we have a ramping value of 100 MW, then going from delivery period 01:00 to 02:00, then the flow value can only change +/- the ramping value from the previous period.\n- **alreadyAllocatedCapacity**: capacity which is already in use. If ramping restrictions exist, then the already allocated capacity needs to be taken into account. This is mostly relevant for intraday auctions where there is planned flows already in place.\n \n**exportsByConnection**\n- **area**: the area exported to\n- **connection**: the named connection to the export area. In some cases, multiple capacity values exist in between two areas - if that's the case, then connection will be used to distinguish the values.\n- **capacity**: the max MW that can be exported on this connection\n- **lossFactor**: in case there is a loss on the cable, then the loss factor tells how much power will be lost. Given a loss factor of 0.02 then 2% of the power gets lost in transit. If we put in 100 MW on the exporting side then 98MW arrives in the import area. \n- **rampingRestriction**: some connections can't change the power flow too quickly. In these cases, a ramping restriction will be present. Ramping restrictions are given in MW, telling how much capacity can change from the previous period. If we have a ramping value of 100 MW, then going from delivery period 01:00 to 02:00, then the flow value can only change +/- the ramping value from the previous period.\n- **alreadyAllocatedCapacity**: capacity which is already in use. If ramping restrictions exist, then the already allocated capacity needs to be taken into account. This is mostly relevant for intraday auctions where there is planned flows already in place.\n \n**importGroupRestriction**\n- **areas**: the areas affected by this restriction\n- **capacity**: the total import capacity that is possible when summing together all area capacities. This is generally larger than a single area capacity, but smaller than the sum of areas.\n\n**exportGroupRestriction**\n- **areas**: the areas affected by this restriction\n- **capacity**: the total import capacity that is possible when summing together all area capacities. This is generally larger than a single area capacity, but smaller than the sum of areas.\n\n**externalImportConstraint**: external import constraints limit the bidding zone net position which represents the total net exchange of the BZ with its neighbors both in FlowBased and ATC network models. The net position is defined as sum \\(export flow\\) - sum \\(import flow\\), and must be higher or equal to -\\(external import constraint\\).\n \n**externalExportConstraint**: external export constraints limit the bidding zone net position which represents the total net exchange of the BZ with its neighbors both in FlowBased and ATC network models. The net position is defined as sum \\(export flow\\) - sum \\(import flow\\), and must be less or equal to \\(external export constraint\\).\n \n**totalImport**: the total available import capacity, taking into account import group restrictions if any exist.\n \n**totalExport**: the total available export capacity, taking into account export group restrictions if any exist.\n \n**dailySummaries**: daily summary value of total import and export capacity, in MWh\n- **totalImport**: total daily MWh import capacity, taking into account import group restrictions if any exists\n- **totalExport**: total daily MWh export capacity, taking account export group restrictions if any exists"
parameters:
- name: market
in: query
required: true
schema:
$ref: '#/components/schemas/AuctionCapacityMarkets'
- name: area
in: query
description: "One area. For example NO1. \n\nSupported: SE(legacy), NO1, NO1A, NO2, NO2_ND, NO2_NK, NO2_SK, NO2A, NO3, NO4, NO5, SE1, SE2, SE3, SE3_FS, SE3_KS, SE3_SWL, SE4, SE4_BC, SE4_NB, SE4_SP, SE4_SWL,\nFI, FI_EL, FI_FS, DK1, DK1_CO, DK1_DE, DK1_KS, DK1_SB, DK1_SK, DK1A, DK2, DK2_KO, DK2_SB, EE, LT, LV, AT, BE, DE_BC, DE_DK1, DE_KO, DE_NK, FR, GER, NL,\nNL_CO, NL_ND, PL, PL_LP, PL_SP, TEL, BG, RO_BG, UK"
required: true
schema:
minLength: 1
type: string
- name: year
in: query
description: 'Year in CET (format: yyyy, e.g., 2024)'
required: true
schema:
type: integer
format: int32
responses:
'200':
description: OK
content:
text/plain:
schema:
$ref: '#/components/schemas/ApiAuctionYearlyCapacity'
application/json:
schema:
$ref: '#/components/schemas/ApiAuctionYearlyCapacity'
text/json:
schema:
$ref: '#/components/schemas/ApiAuctionYearlyCapacity'
'401':
description: Unauthorized
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'403':
description: Forbidden
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'400':
description: Bad Request
content:
text/plain:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
application/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
text/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
/api/v2/Auction/FlowBasedConstraints/ByDomain:
get:
tags:
- Auction
summary: Flow-based Constraints
description: "Returns a list of flow-based constraints per market, date and one domain\n \nFlow-based capacity constraints represent limits on critical network elements in the power grid. Flow-based constraints are used in combination with ATC capacities to calculate flows inside of flow-based regions.\n \nFlow-based capacity constraints are given per delivery period. Each period contains multiple constraints, and each constraint consists of:\n- **RAM (Remaining Available Margin)** - the available margin for the critical network element, which serves as an upper bound on the total consumption of this element by different bidding areas.\n - A list of **PTDFs (Power Transfer Distribution Factors**) for each Bidding Zone in the corresponding Flow-Based region. A PTDF indicates how much a bidding zone's Net-Position contributes to the load of the critical network element (limited by RAM).\n \nTo see if a constraint is binding (or how close it is to being reached), multiply the Net-Position (NP) for each Bidding Zone by its respective PTDF. Then, sum the results of each multiplication. This must result in a value that is lower or equal to the RAM.\n \nWhen the sum equals the RAM, the corresponding constraint (CNEC) is binding. This can be exemplified by the following formula:\n \n`PTDF1 * NP1 + PTDF2 * NP2 + ... + PTDFn * NPn ≤ RAM`\n \nEuphemia ensures that these constraints will always be respected.\n \nThe Net-Position of a Bidding Zone is defined as Total Export - Total Import for a Bidding Zone. In our data model, this is easiest gotten from the Flow model, and refers to -(totalNetPosition) for each delivery period and area.\n \n### Response field descriptions\n**periods**: a list of delivery periods. Each period has\n- **deliveryStart**: the start time of the delivery period\n- **deliveryEnd**: the end time of the delivery period\n- **constraints**: a list of constraints.\n \nEach constraint consist of:\n- **id**: an identifier for the unit. Note that this id is only to identify the constraint within this market coupling session\n- **name**: an optional name for the unit, not always present\n- **remainingAvailableMargin**: the RAM value, described above\n- **powerTransferDistributionFactors**: a list of Power Transfer Distribution factors for each area, described above"
externalDocs:
description: Flow based description
url: https://developers.nordpoolgroup.com/reference/auction-flow-based-constraints-data
parameters:
- name: market
in: query
required: true
schema:
$ref: '#/components/schemas/AuctionFlowBasedConstraintMarkets'
- name: flowBasedDomain
in: query
required: true
schema:
$ref: '#/components/schemas/FlowBasedDomainType'
- name: date
in: query
description: Delivery date, referring to CET date. Format yyyy-MM-dd, for example 2024-08-15
required: true
schema:
type: string
format: date
responses:
'200':
description: OK
content:
text/plain:
schema:
type: array
items:
$ref: '#/components/schemas/ApiFlowBasedConstraint'
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ApiFlowBasedConstraint'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/ApiFlowBasedConstraint'
'401':
description: Unauthorized
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'403':
description: Forbidden
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'400':
description: Bad Request
content:
text/plain:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
application/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
text/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
/api/v2/Auction/Flows/ByAreas:
get:
tags:
- Auction
summary: Auction Flows
description: "Returns a list of auction flows per area for a market, date and list of areas.\n \nFlows are describing how much power are exchanged in between areas.\n \nThis is the flow coming from Euphemia - note that in the Nordic region a post coupling calculation is done to adjust this flow. See Scheduled Physical Flows for Nordic Day-ahead flows after 30th of October 2024.\n \nFlows are always described from an area point of view. Some flows will have a loss on the cable - imports in an area is always after losses, and exports are before losses.\n \n### Response field descriptions\n- **status**: Missing if data does not exist. Preliminary if the market coupling session is not complete. Final once the market coupling session is complete. Cancelled if the auction is cancelled.\n- **dailyTotalImport**: total MWh imported volume\n- **dailyTotalExport**: total MWh exported volume\n- **dailyTotalNetPosition**: total net position in MWh (total import - total export).\n \n**flows**: a list of delivery periods, containing all flows for that period\n- **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\n- **totalImport**: sum of all connection import volumes given in MW\n- **totalExport**: sum of all connection export volumes given in MW\n- **totalNetPosition**: total import - total export"
externalDocs:
description: Data portal link
url: https://data.nordpoolgroup.com/auction/day-ahead/flows?deliveryDate=latest&deliveryArea=EE&displayImportExport=false
parameters:
- name: market
in: query
required: true
schema:
$ref: '#/components/schemas/AuctionFlowMarkets'
- name: areas
in: query
description: 'Comma-separated list of areas (e.g., NO1, NO2).
Supported: SE(legacy),NO1,NO2,NO3,NO4,NO5,SE1,SE2,SE3,SE4,FI,DK1,DK2,EE,LT,LV,AT,BE,FR,GER,NL,PL,UK,TEL,BG'
required: true
schema:
minItems: 1
type: string
items:
type: string
- name: date
in: query
description: Delivery date, referring to CET date. Format yyyy-MM-dd, for example 2024-08-15
required: true
schema:
type: string
format: date
responses:
'200':
description: OK
content:
text/plain:
schema:
type: array
items:
$ref: '#/components/schemas/ApiFlow'
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/ApiFlow'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/ApiFlow'
'401':
description: Unauthorized
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'403':
description: Forbidden
content:
text/plain:
schema:
type: string
application/json:
schema:
type: string
text/json:
schema:
type: string
'400':
description: Bad Request
content:
text/plain:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
application/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
text/json:
schema:
$ref: '#/components/schemas/ValidationProblemDetails'
/api/v2/Auction/Flows/Yearly/ByArea:
get:
tags:
- Auction
summary: Yearly Auction Flows
description: "Returns a list of auction flows for a market, year and one area.\n \nFlows are describing how much power are exchanged in between areas.\n \nThis is the flow coming from Euphemia - note that in the Nordic region a post coupling calculation is done to adjust this flow. See Scheduled Physical Flows for Nordic Day-ahead flows after 30th of October 2024.\n \nFlows are always described from an area point of view. Some flows will have a loss on the cable - imports in an area is always after losses, and exports are before losses.\n \n### Response field descriptions\n**dailySummaries**: contains a list of daily summaries for all flows for that day\n- **totalImport**: total import volume for the day, in MWh\n- **totalExport**: total export volume for the day, in MWh\n- **totalNetPosition**: total net position for the day (total import - total export), in MWh\n- **connectionSummaries**: list of all connections used for the day, with total imports and exports given in MWh \n \n**flows**: a list of delivery periods, containing all flows for that period\n- **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\n- **totalImport**: sum of all connection import volumes given in MW\n- **totalExport**: sum of all connection export volumes given in MW\n- **totalNetPosition**: total import - total export"
parameters:
- name:
# --- truncated at 32 KB (98 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/nordpool/refs/heads/main/openapi/nordpool-auction-api-openapi.yml