Realtime Electricity Market Data

A separate API service is available for retrieving realtime electricity market data. The API service is monitored 24/7. The Terms and conditions of use of data and Privacy Policy for Energi Data Service also apply for this API service.

Limits on Requests

The data sources are updated at the earliest once per minute, and you should not make excessive requests that could overload the system. Hence, the recommended maximum request rate is 1 request per second.

Updates

The public API may be updated with new datasets in the future.

Available datasets

The public API provides access to various datasets related to the Danish energy system, and they are provided as close to real-time as possible.

mFRR Request

Description mFRR (Manual Frequency Restoration Reserve) Request is the current amount of mFRR needed to bring the system in balance; specifically it is the amount of mFRR needed forwarded to the AOF, the optimization function that selects the cheapest resource to bring the system in balance. It is updated every minute. However, for a given MTU the values are not published until 7.5 minutes before start of the MTU.
Dataset name mfrrRequest
Each data point contains the following fields:
timeStamp The timestamp of when the mFRR Request was issued to the AOF.
mtuStart The start of the 15 minute MTU.
values An array of objects, each containing:
  • area: The area / bidding zone (DK1 or DK2).
  • value: The amount of mFRR requested in MW (can be positive or negative).

Request methods

To get a graphical guide to the API, you can access our swagger documentation.

The API is a synchronous interface with HTTP GET. Parameters are part of the URI string. It is designed to be simple and easy to use, allowing you to retrieve data in a straightforward manner. The base url for all requests is:
To get the latest values you can use the "latest" API endpoint:
To include historial data values you can use the "period" filtering API endpoint. It will return the latest values for the specified period:
The {From} parameter can be replaced with a specific date-time-offset. This cannot be a date in the future.

The {To} parameter can be replaced with a specific date-time-offset. This cannot go further back than 7 days from the current date.

Examples of valid datetime values:
  • 2025-08-01T09:05:00Z (09:05 UTC)
  • 2025-08-01%2011:05:00%2B02:00 (11:05 UTC+2 hours, i.e. local Danish time)
To include all historical data values you can use the "lastweek" API endpoint. It will return all available data, i.e. 7 days:
The {Dataset} parameter can be replaced with the name of the dataset you want to access, i.e. mfrrRequest.

You can also use the value all keyword to get the latest values for all available datasets. The Dataset value is case-insensitive, so you can use either uppercase or lowercase letters.

Examples

all available datasets

To get the latest values for all available datasets:


latest values

To get the latest values only for a specific dataset:


specific time period

To get all the values from 2025-08-22T06:45:00Z to 2025-08-23T05:00:00Z for a specific dataset:


error response

Error response example - RFC 9457 standard