GET /market-access/v1alpha1/timeseries/series/aggregate-allocations now
gives the control area of German aggregate allocations in market_meta, as
control_area. For a series of one metering grid area, it is the control
area that the grid area is in. To select the aggregate allocations of one
control area, filter by market_meta=control_area:10YDE-RWENET---I.GET /market-access/v1alpha1/timeseries/allocations and
GET /market-access/v1alpha1/timeseries/aggregate-allocations now give each
value a stated_at, the market’s timestamp for that version of the value.
The current value of a settlement period now follows the market’s order, so a
correction replaces the value it corrects even when it arrives first.
known_at still tells you when Engrate received each value.GET /market-access/v1alpha1/timeseries/allocations now gives each value a
finality: how final the settlement run is that the value comes from, such
as preliminary or final, or null for a value that comes from no
settlement run. The values of each settlement
period come with the current value first: the highest finality, then,
among values without a finality, the most trusted quality, then the
latest known_at. A later settlement run now replaces an earlier one, also
when its quality is lower.GET /market-access/v1alpha1/timeseries/imbalance gives the imbalance of
your balance groups per scheduling area and settlement period, as the market
settles it, and the adjustments that the market included in it. On a total,
a positive volume means that the balance group was long. On an adjustment, a
positive volume makes the balance group longer. Each run of the settlement is
one record: use the highest finality, then the latest stated_at, and on
a tie the first record in the response.
GET /market-access/v1alpha1/timeseries/series/imbalance lists the series.GET /market-access/v1alpha1/timeseries/confirmed-schedules gives the
values that the Scheduling Area Responsible uses for your schedules: one
record for each series and 15-minute period where a value or a rejection is
in force, with its kind (confirmed, modified, imposed or rejected),
the energy in Wh, and whether the confirmation is final. One request covers
up to 32 days.
GET /market-access/v1alpha1/timeseries/series/confirmed-schedules lists
the series.POST /schedule-management/v1/schedules now rejects amounts the market
cannot carry instead of silently rounding them, returning HTTP 400 with the
first quarter-hour that does not fit. For each quarter-hour, the Netherlands
market carries multiples of 0.004 MW (1 kWh), and the German market carries
multiples of 0.001 MW (at most three decimal places). Amounts that fit are
sent unchanged.GET /market-access/v1alpha1/timeseries/aggregate-allocations now gives the
aggregate allocations that the Dutch grid operators send to your balance
responsible party: per grid area, supplier and allocation group, in 15-minute
periods. Profiled allocations also carry their profile category and offtake
type in market_dimensions.
GET /market-access/v1alpha1/timeseries/series/aggregate-allocations lists
them. Every run of one aggregate has the same external_id, and its
finality tells the first run from the revised and final ones.Core data now has the Swedish system operators Coala AB and Vindlänken Elnät AB
and their metering grid areas GUK and VIF, and the scheduling areas ALPACA,
CNE and FCRC.
GET /market-access/v1alpha1/timeseries/aggregate-allocations and
GET /market-access/v1alpha1/timeseries/series/aggregate-allocations now
take a market_meta filter, as key:value, for example
market_meta=summed_series:ZA0. An aggregate allocation matches when it
carries every pair.GET /market-access/v1alpha1/timeseries/allocations now gives the allocated
volumes of your Dutch accounting points, as the grid operator sends them:
consumption and production in 15-minute periods. Each series carries the
GSRN of its accounting point, and
GET /market-access/v1alpha1/timeseries/series/allocations lists them, so
you can find a series by its GSRN.The schedule page has three tabs. Series gives the match status, the
confirmation and the finality of each series. Open a series to see your
values, the values of the counterparty and the confirmed values as a chart and
a table. Versions gives each version that you submitted, with its answer, and
shows the active version. History gives each version, match report and market
message. Open a match report or a market message to see the message as
Engrate received it. The charts give the time of day in the time zone of the
market, whatever the time zone of your browser.
For each schedule, the Schedules page now gives the latest version and the
answer to it, the active version, whether the series match, and the
confirmation and finality of the series.
Each series of a schedule version now gives
market_agreement_id, in the
version spec and in the ids of
GET /schedule-management/v1/schedule-series/{version_uid}. An external or
foreign series gives the value as you submitted it, also an empty string. A
series with no market agreement gives null. Thus you can tell apart two
external series that have the same areas and parties.Each message in
GET /schedule-management/v1/schedules/{uid}/incoming-messages
now gives version: the schedule version that the message answers. It is
null if the message names no single version of yours, and always null for
a German anomaly report. If the match report read from that report is about
one version, the match report gives the version.GET /schedule-management/v1/schedules/{uid}/reports is a new alpha endpoint.
It gives a summary of each match report of a schedule, for all versions and
for the reports that name no version: what the report is, when it was stated
and which version it is about, without its verdicts.A new alpha endpoint gives one market message that the Scheduling Area
Responsible sent about a schedule, as Engrate received it.
GET /schedule-management/v1/schedules/{uid}/incoming-messages/{message_uid}
takes the uid of the message from List Incoming Messages, or the
incoming_message_id of a match report.Two new alpha endpoints show the information that the Scheduling Area
Responsible gave about your schedules.
GET /schedule-management/v1/schedules/{uid}/series-state gives the match
status of each series, with the findings of the Scheduling Area Responsible.
It also gives the values that the Scheduling Area Responsible will use. Each
match report in the series state gives the version that the report is
about, and its kind.
GET /schedule-management/v1/schedule-versions/{version_uid}/reports gives
the match reports for one schedule version.POST /schedules now returns 400 Bad Request when two series in a request
describe the same flow: two production or two consumption series in one
scheduling area, two internal series with the same area, in_party and
out_party, or two external or foreign series with the same in_area,
out_area, in_party, out_party and market_agreement_id.The console now asks which market to open on the first time you sign in. It
remembers the choice, and you can change it at any time from the market menu
in the top bar.
Schedules, Settlement and Configuration are now separate pages in the console,
in place of the single tabbed view. The new experience contains both usability
and performance fixes.
The API now enforces a request rate limit per credential. Requests over the
limit get a
429 Too Many Requests response with a Retry-After header.The console has a new Core section where you can find parties, bidding zones,
scheduling areas, control areas, and metering grid areas.
The console has a new top bar and left navigation. The navigation groups pages
by what you use them for, shows icons only on medium screens, and opens as a
drawer on small screens. Breadcrumbs have moved into the top bar, which stays
in place as the page scrolls.
New
GET /core/v1/control-areas endpoint lists ENTSO-e control areas — the
grid a single TSO operates — identified by EIC code.New
GET /core/v1/bidding-zones endpoint lists European bidding zones (price
areas) such as SE3 and NO1, identified by EIC code. Filter by EIC, name,
or country (ISO 3166-1 alpha-2).The Cost of Energy Cost Calculation workflow is now available in Console as a
beta feature. You can select an MGA and tariff, provide required datasets via
pasted values, CSV upload, or reusable profiles, and calculate component-level
and total costs for a selected period in one guided flow.
The Cost of Energy console now includes a dedicated Profiles page where you
can create, edit, and delete reusable time-series profiles. Profiles can be
used to represent your energy offtake from or injection to the grid in tariff
cost calculations.
The clearing periods table in the DE Settlement tab is now clickable. Each row
opens a detail page showing the period status, total imbalance and cost, MaBiS
deadlines (M+18 / M+30 / M+42) with relative-time hints, and tabs for daily
settlements, objections, EDIFACT messages, and per-day imbalance.
You can now create, update, and delete custom profiles via the API. Profiles
store timeseries data (e.g. energy offtake, spot prices) that can be
referenced in tariff cost calculations instead of sending inline data arrays.
Several pre-built global profiles are also available for common scenarios like
villa and apartment offtake, facility injection, and uniform spot prices.
The system operator page now includes a “Rate Profile” tab showing energy
(SEK/kWh) and power (SEK/kW) rates over time as step charts.
New
GET /core/v1/holidays endpoint returns public holiday occurrences for
a year range. Filter by country (ISO 3166-1 alpha-2) and/or specific holiday
identifiers (e.g. se/julafton). Each occurrence carries the IANA timezone
in which the holiday is observed.Four new registered datasets now support tariffs with a conditional
(villkorad / secunda) capacity tier on top of firm (prima):
yearly-conditional-subscribed-offtake-capacity and
yearly-conditional-subscribed-injection-capacity hold the contracted
conditional levels and drive the conditional subscription fee;
hourly-available-conditional-offtake-capacity and
hourly-available-conditional-injection-capacity carry the real-time
available capacity per hour, so overdraft calculations automatically
account for DSO-initiated curtailment.Free users can now browse all system operator pages. Tariff names and component
structure are visible for every operator; detailed data (cost calculations,
visualizations, and explanations) is available on a paid plan.
DE schedule submissions now validate party and area EICs against AG-FPM v4.6
Appendix F before sending to the TSO. Non-compliant production, consumption,
internal, and external series are rejected with a descriptive error message.
Schedule submissions are now rejected if the time series does not start at 00:00
Europe/Berlin for the declared delivery date, enforcing the AG-FPM v4.6 requirement
that schedules cover the complete delivery day.
Clicking a row in the NL imbalance settlement table now expands an inline detail
view showing all time series for that report, including business type, value
(volume or price), point count, resolution, and reason text. You can pick a series
to see quarter-hourly values in a bar chart with the correct unit (MWh or EUR/MWh).
Dutch (TenneT) imbalance reports are now visible in the Settlement tab. Switch
to the NL market to browse daily AIM reports, view status and document IDs, and
filter by date range. New REST endpoints under
/nl/settlement/imbalance-reports
expose the same data programmatically.The Electricity Area Map plugin has been sunsetted. Area and boundary data is now available through the geodata endpoint in the Core plugin.
New organizations now automatically receive access to the Core plugin upon signup,
providing core platform data alongside the existing default plugins.
Fixed incorrect unit conversion in schedule submissions: German TSO schedules were
erroneously multiplied by 4; Dutch TenneT schedules used an incorrect MWh→kWh factor.
Dutch (TenneT) schedules now show time series data in the console and emit
audit trail events for each TSO response (ACK, ANO, RI, CNF). The status
pipeline now progresses correctly past “ingested” for NL schedules.
Energy market parties (TSOs, DSOs, and other grid operators) now include
English descriptions, official website URLs, and logo URLs in the parties API,
powered by automated enrichment.
Schedule Management now implements AG-FPM v4.6 process-phase-aware gate
closure with separate handling for day-ahead, DA matching, and intraday phases.
New audit trail events cover declared-limit breach warnings (A59),
fault-tolerant acceptance (A57/A21), no-ACK timeout detection, and intraday
submission advisories (close-to-QH and multiple-versions-per-QH).
Stronger validation and rate limiting for German schedule submissions to
prevent rejected deliveries and improve reliability during intraday trading.
We’ve launched console.engrate.io - a completely redesigned application replacing the previous app.engrate.io. The new console features a modern design system and serves as the central hub for all Engrate products.What’s new:
- Refreshed dashboard with improved navigation and overview of your resources
- Power Tariff management now fully integrated in the console
- Schedule Management with audit logs, debugging tools, and detailed views
app.engrate.io now automatically redirects to console.engrate.io.
New endpoint to retrieve public and bank holidays for supported countries. Useful for tariff calculations where holiday pricing differs from regular weekday rates.Check out the holidays endpoint.
Power Tariff now supports price levels with a configurable price tier system. You can choose between:
- No tiers - Single flat-rate pricing
- Stacked - Each tier applies only to power within its range
- Stepwise - Entire power is charged at the rate of the tier it falls into
The Power Tariff product has been extended with The Engrate Power Tariff Calculator Engine and is now readily available for your calculation needs.Check out the calculation endpoint.
Power Tariff is now out of Early Access! Go build!Early Access customers can safely switch from:
api.ea.engrate.iotoapi.engrate.io
A new model for Power Tariff is now out. We’ve redesigned it to make it simpler based on customer feedback.Check out the updated documentation here:https://docs.engrate.io/api-reference/get-by-mga-code
Today we’re adding Electricity Area Map. This product provides comprehensive access to electricity area boundaries from all Swedish Distribution System Operators (DSOs), Market Balance Areas (MBAs), and Market Grid Areas (MGAs).Check it out here:https://docs.engrate.io/api-reference/list-areas
The Power Tariff product is now live in early access!You can sign up for it here: https://engrate.io/effektavgifter