Confirmed market values take priority for the hours that have already been published.
Forecast API · Commercial use
Turn electricity-price forecasts into better charging decisions
Published day-ahead prices stop where the market has not settled yet. Our API extends that open horizon with price and CO2 forecasts, then turns both known and predicted values into answers such as “charge today or tomorrow?” and “which four-hour window is cheapest?”.
- Forecast beyond day-aheadUp to 120 hours for planning across several days
- Decision-ready resultsCheapest, greenest and combined time windows
- Quality you can inspectRolling, settled forecast and decision metrics
One continuous planning horizon
Where published prices end, the forecast begins
We do not present every future value as equally certain. Official day-ahead values are used wherever they exist. The model forecast then fills the still-unknown hours, and the decision layer evaluates the complete horizon.
Model output extends the unknown part of the horizon so products can plan beyond tomorrow.
Return the best time window, whether it is active now, or which of two days is cheaper.
No blurred boundary: each price entry identifies its source, so your product can distinguish published day-ahead values from forecast values in charts, automations and customer communication.
Current evidence · Germany
Forecast quality measured against settled outcomes
The forecast is frozen before delivery and compared with the day-ahead prices published later. This scores the decision a customer actually makes—not only whether every hourly number was exact.
These figures update with the rolling sample. Open the underlying API response.
Product outcomes
Answers your customers can act on
Raw market data still leaves the important product question unanswered. The API provides the series, ready-computed windows and quality context needed to turn a forecast into a clear recommendation.
cheaper_day_decision also reports how often following the forecast selected the cheaper day.What the API provides
The structured quality blocks include forecast_quality, hourly_accuracy and cheaper_day_decision when sufficient settled observations exist. Full field reference in the OpenAPI specification.
Who this is for
The same API surface serves Home Assistant, evcc, ioBroker, Node-RED, openHAB and Homey integrations and includes source, freshness and access metadata for operational monitoring.
Supported market areas
The list below is generated from the same market configuration as the public price endpoint on every website deployment. New price zones therefore no longer need to be maintained in this page by hand.
Loading the current market list…
Availability can differ by feature: the catalog describes the price forecast. Retail-price estimates and other optional fields are available only for their respective supported markets.
How access works
There is no flat self-service plan for commercial use yet. Tell us briefly what you need the data for - use case, relevant markets and rough request volume is enough to start. We'll follow up with terms that fit.
The email request is non-binding. For purely private, non-commercial automation, the ready-to-book Private Pro access already exists.