BilateralTransaction

Package: PowerOperationsOpenAPIModels · Source: Operations/Market/BilateralTransaction.json

A bilaterally negotiated trade reported into the settlement ledger. Settlement-only: it carries no power-balance impact and never clears against a market model. It exists for round-tripping submissions and offline settlement.

Properties

Property	Type	Required	Unit	Description
id	integer	yes	—	Unique integer identifier for this component.
name	string	yes	—	Name of the component. Components of the same type (e.g., PowerLoad) must have unique names, but components of different types (e.g., PowerLoad and ACBus) can have the same name.
seller_id	string	yes	—	External participant identifier for the selling counterparty, as reported on the transaction. Not a component reference: sellers are not represented in the entity registry.
buyer_id	string	yes	—	External participant identifier for the buying counterparty, as reported on the transaction. Not a component reference: buyers are not represented in the entity registry.
from_id	integer	yes	—	ID of the source location, resolved through the entity registry: a topology record or a trading hub.
to_id	integer or null	—	—	ID of the sink location, resolved through the entity registry: a topology record or a trading hub. null for a single-location trade.
product	string (BilateralProduct)	yes	—	Traded product.
market	string (MarketStage)	yes	—	Market stage the transaction was reported against.
confirmation	string (BilateralConfirmation)	yes	—	Confirmation status the transaction settled under.
max_active_power	number	yes	MW	MW envelope of the transaction. Units: MW.
active_power_association_id	integer or null	—	—	Store-minted id of the time series supplying the trade’s delivered active-power schedule, or null when max_active_power alone describes the trade.