> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trlyr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# June 5, 2026

> A new, simplified ancillary services suite: unified ancillary service endpoint, new operational data categories for ancillary commitments, available wholesale capacity, and cross-market validation.

### New features

**A new, simplified ancillary services suite**

We have been working on making ancillary services far easier to integrate, and this week we are rolling out a new suite of simplified, customer-facing endpoints. The number of endpoints you need to implement to run ancillary services drops from 14 down to just 4. For new customers this dramatically speeds up onboarding, and for existing customers it offers a much simpler path if you would like to migrate.

The suite has two parts: a single unified endpoint for submitting, reading bids and ultimately reading results. And a set of new ancillary data categories on the virtual asset operational endpoint that give you everything you need to decide what to bid — all from the route you already use for operational data.

We recommend having a read through the full guide here: [Ancillary services at the virtual asset level](/layrUserGuide/features/ancillary-services-virtual-asset-level).

**Unified ancillary bids endpoint**

After having published the get endpoints for ancillary services two weeks ago, we have added a new `POST /organisations/{organisationID}/virtual-assets/{virtualAssetID}/ancillary/bids` endpoint for submitting ancillary bids across FCR, aFRR Capacity, and aFRR Energy through a single route. This one endpoint replaces the separate per-product flows you previously had to wire up individually.

The endpoint combines create and update behavior: if bids have already been submitted for a product, they are replaced by the new submission, so you do not need to track whether a bid already exists. FCR and aFRR bids must be submitted in separate requests.

The already existing get endpoint returns the submitted bids with three additional response fields: `bidID` (the unique bid identifier), `market` (one of `FCR`, `AFRRCapacity`, `AFRREnergy`), and `status` (either `pending` or `submitted`). A `pending` status indicates the bid is still being placed with the TSO and cannot be updated in the meantime.

More details: [Ancillary services at the virtual asset level](/layrUserGuide/features/ancillary-services-virtual-asset-level).

**Navigating ancillary services from the operational endpoint**

To support an easier bidding flow, we have added several ancillary data categories directly to the virtual asset operational endpoint, so you can see your commitments and available capacity from the same route you already use for operational data — no need to query individual blocks or piece together multiple calls.

Active market commitments are now available on `/organisations/{organisationID}/virtual-assets/{virtualAssetID}/operational` and `/operational/latest`:

* `fcrCommitment`: committed FCR capacity in kW. Reflects the total bid capacity before the auction clears, and the accepted commitment once it does.
* `afrrPosCommitment`: committed aFRR positive (discharge) capacity in kW.
* `afrrNegCommitment`: committed aFRR negative (charge) capacity in kW.

Alongside these, the remaining wholesale capacity after ancillary reservations is also available on both endpoints:

* `wholesalePowerCapacityChargeAvailable`: charge capacity available for wholesale trading, reduced by FCR and aFRR Neg commitments.
* `wholesalePowerCapacityDischargeAvailable`: discharge capacity available for wholesale trading, reduced by FCR and aFRR Pos commitments.

We recommend monitoring these five categories together to track how ancillary bids affect your available wholesale capacity in real time.

**Cross-market capacity validation made simple**

When placing aFRR bids you previously had to satisfy two separate capacity checks: an individual-market check and a cross-market check (the maximum total ancillary capacity ceiling). We have added two operational data categories that combine both into a single value, so bidding up to these limits guarantees your aFRR bids pass both validation steps without any separate queries.

Available on the operational endpoint (`/organisations/{organisationID}/virtual-assets/{virtualAssetID}/operational`):

* `afrrPosCapacityAvailableMinusFcr`: maximum aFRR positive capacity available for bidding, after accounting for FCR commitments and the total ancillary capacity ceiling.
* `afrrNegCapacityAvailableMinusFcr`: maximum aFRR negative capacity available for bidding, after accounting for FCR commitments and the total ancillary capacity ceiling.

Together with the unified bids endpoint, these categories mean a complete ancillary workflow. You can check available capacity, submit a bid, monitor your commitments through just a handful of calls on routes you already know.