Create FCR bids for a given virtual asset.
Creates fCR bids for a virtual asset
The endpoint expects a list of fCR bids. For now, only a single bid per product is allowed.
If one (or more) bids have already been submitted for the product, they will be replaced by the newer submission.
Request body
The request body is a list of fCR product bids you would like to place.
product: The EFA-block based product for which the bids are placed. It must be in the following format: NEGPOS_{{startEfaBlock}}_{{endEfaBlock}}, e.g. NEGPOS_00_04 for a bid in the first EFA block of the day (00:00-04:00 am). The sixth and final EFA block is NEGPOS_20_24.
deliveryDay: The delivery day of the bid. It must be in the format YYYY-MM-DD, e.g. 2026-05-30 (full day according to RFC3339).
bids: A list of individual bids for the product.
Each bid in the list contains the following fields:
offeredCapacity:
The offered capacity of the bid in kilowatts, e.g. 2000.
The value must be an integer multiple of 1 megawatt. Any non-integral part will be rounded down, e.g. 1000.5 is accepted and rounded down to 1000kW, whereas 1500 would be rejected.
capacityPrice:
The capacity price of the bid in EUR/MW/h, e.g. 100.00.
This price is used to determine the position of the bid in the TSO’s merit order.
The max price that can be bid into both markets is 15,000 Euros, the min price is -15,000 Euros.
If you bid a positive price (> 0), you will be paid by the TSO. If you bid a negative price (< 0), you pay the TSO.
Bidding deadline
All bids must be placed before the following deadline: 7:30 am CET/CEST on the day before delivery. The auction opens a week before the delivery day.
Determining available bidding capacity
Validation 1 and 2 must be passed, or the bid will be rejected.
Validation 1: Available fCR capacity timeseries
The offeredCapacity for fCR bids at any given point in time must be lower than or equal to the available fCR capacity of the virtual asset.
The value can be retrieved from the operationalData endpoint on the virtual asset as a 15 minute timeseries by requesting the operational data category fcrCapacityAvailable.
Example:
fcrCapacityAvailablefrom 00:00-04:00 am: 4000 kW- Remaining capacity for product
NEGPOS_00_04: 4000 kW
Validation 2: Max total ancillary capacity timeseries
The offeredCapacity for fCR bids at any given point in time must also take into account bids that have already been placed in the aFRR market for the same period so as not to exceed the max total ancillary capacity of the virtual asset.
An aFRR bid has either a positive or a negative product direction, while an fCR bid has both product directions.
The max total ancillary capacity can be retrieved from the operationalData endpoint on the virtual asset as a 15 minute timeseries by requesting the operational data category maxTotalAncillaryCapacityChargeAvailable (negative direction) and maxTotalAncillaryCapacityDischargeAvailable (positive direction) respectively. The lower of those two values will determine the remaining fCR capacity.
Example:
maxTotalAncillaryCapacityDiscargeAvailable: 5000 kWmaxTotalAncillaryCapacityChargeAvailable: 4000 kW- aFRR Pos bid placed for product
POS_00_04: 3000 kW - Remaining capacity for product
NEGPOS_00_04: 1000 kW (minimum(5000,4000) - 3000)
Deleting bids
To delete a bid, set the bid body as an empty array:
[
{
"bids": [],
"deliveryDay": "2026-04-10",
"product": "NEGPOS_00_04"
}
]
Adjustment of virtual asset blocks
Once a valid bid has been submitted, a new fCR block ("market":"FCR") is added to the virtual asset.
The block will cover the duration of the whole virtual asset.
Inside the block’s power capacity timeseries, the powerCapacity is updated to value of the bid’s offeredCapacity for the delivery period of the product you bid on.
At the same time, the powerCapacity of the wholesale block ("market":"WHOLESALE") for the delivery period of the product you bid on is reduced by the offeredCapacity.
Both the fCR and the wholesale block will be adjusted according to the incoming bid results.
E.g. if a bid is rejected, the powerCapacity is removed from the fCR block and added to the wholesale block.
Response format
Returns a JSON representation of the created fCR product bids identical to the request body, except for one additional field:
productDateCode: The productDateCode in the response references a specific product on a given delivery day: e.g. 2025-01-01_NEGPOS_00_04. This “product-date-code” can be used to update the bid individually through the PUT endpoint.
Headers
Access token
Path Parameters
Organisation ID
Virtual Asset ID
Body
Bids to be created