The access to the REST API (v1) will be granted until 30 June 2026. 

We will integrate new trading products with expected go-live dates until 31 March 2026. For those products where the go-live date is delayed until April or original plans for go-live dates were set for the second quarter, support will not be provided. Therefore, we recommend starting as early as possible with the technical migration to the revamped REST API (v2). 

This is an application independent from the new REST API (v2). The sFTP server will remain accessible until further notice. As a matter of principle, EEX will provide sufficient time in case of migration.  

Despite our efforts in the past years to keep high standards in place, the rise in available information and the increasing number of clients has put the underlying infrastructure under stress. The architectural analysis has shown that we have to take it to the next level in terms of data supply, data storage and processing capacity and better leverage cloud technology for the underlying infrastructure.  The migration to our revamped REST API (v2) will address these concerns and allows seamless usage to a continuously larger user pool.  

This shift to the revamped REST API (v2) will drastically improve the technical performance but will also change API calls for the outlined reasons.   

Scalable infrastructure with direct connection to source systems, designed to handle high loads efficiently and ensure consistent availability even under peak demand. 

OpenAPI standard, offering a well-known and widely adopted specification that simplifies integration and enables more user-friendly documentation. 

Extended data access, including new endpoints such as Top-of-Book, which delivers real-time insights into the highest bid and lowest ask prices in the order book. 

In principle, you can expect the same data in both REST APIs. However, the data presented in the revamped REST API (v2) is more granular than before, especially in terms of reference data and the display of spread trades. 

However, methods differ to a certain extent which makes it necessary to carefully doublecheck that the same things are requested. If you think that data nevertheless differs, please report these cases to us for quality check. We will report the results back to you at the earliest date possible.  

The EEX Group DataSource REST API (v2) User Guide has a ‘Good to Know’ section with more detailed information. 

Market Data is available from 1 November 2020 onwards. 

Transparency Data is available from January 2019 onwards. 

More detailed information is available in the EEX Group DataSource REST API (v2) User Guide.

The EEX Group DataSource REST API (v2) is designed to be accessible and useful for real-time information on Market, Index, and Transparency Data. Real-time data should be understood to mean that no intermediate step is built between data creating in the origin-system and the REST API (v2). The timing of the results delivery depends on the internet connection itself, the concurrent number of active users and the scope of the REST API (v2) request. The larger the data request, the more time it will take. 

Due to the availability of a wider range of parameters in the revamped REST API (v2) users can make API requests for their individual use cases and benefit from the lowest response time.  

The revamped EEX Group DataSource REST API (v2) introduces a more structured and standardised approach to data access. Queries now follow a more clearly defined logic and are built using short codes combined with more readable maturities, e.g. DEBM 202510, replacing the previous "Products", e.g. /E.DEBMZ25, and "Root", e.g. DEBM logic. This makes requests more specific, predictable, and easier to maintain. 

Users can retrieve available short codes directly via reference data endpoints. These endpoints provide full visibility into valid combinations of market areas, instruments and maturities, enabling an iterative query process that reduces inefficiencies. 

Broader data availability, with significantly more fields and information accessible across multiple endpoints. 

OpenAPI standard, ensuring a consistent and widely recognised specification that simplifies integration and improves documentation usability. 

Dedicated EEX Group DataSource Hub website, where users can find the full documentation, explore endpoint structures, field definitions, and obtain their API key. 

Authentication via API keys, replacing the previous username/password method for improved security and flexibility. 

OpenAPI standard, ensuring a consistent and widely recognised specification that simplifies integration and improves documentation usability. 

The API endpoints for reference data, Urgent Market Messages (UMM) data and time series data which will require the country to be specified directly in the queries. 

All asset-relevant reference data is now included directly in the UMM data set. 

There are dedicated endpoints for getting latest UMM data and for getting relevant data for a certain period. 

Enhanced company-, facility-, and unit specific reference data due to additional fields (e.g. EIC, Unit of Measurement, ...). 

The UMM data query logic has changed, making it possible to output all available events from a defined point in time. 

All data points, including trade prices, settlement prices, indices, will be provided immediately once computed. Details can be found in the new EEX Group DataSource REST API (v2) User Guide.

Reference data on instrument level for EEX Derivatives  and EEX Natural Gas & EEX Environmental Spot markets for every EEX exchange trading day. 

Trade data for EEX Derivatives and EEX Natural Gas & EEX Environmental Spot markets. Granularity is in microseconds. 

Settlement Prices for EEX Derivatives and EEX Natural Gas & EEX Environmental Spot markets. 

Intraday Statistics for EEX Derivatives and EEX Natural Gas & EEX Environmental Spot markets. 

Top-of-Book information for EEX Derivatives and EEX Natural Gas & EEX Environmental Spot markets. Granularity is in microseconds. 

Indices data for EEX Derivatives & Spot markets. 

Transparency Data on the capacity, availability and usage of power and natural gas production, consumption, storage and transmission units. 

We can confirm that it is the clear intention to integrate all indices in the same way in the revamped REST API (v2) and to decommission the interim solutions with downloadable files on EEX website. 

However, parallel to the revamped REST API (v2) roll-out, we also renew our index computation infrastructure and bundle index computations in one central location. 

Therefore, for an additional period, interim solutions will be still in place before they are stepwise integrated into the central index solutions. This applies to EEX Next Day Index – NDI, EEX Neutral Gas Price – NGP (ETF, TTF) and EEX KWK Index as downloadable files on the website. 

EEX HYDRIX, EEX Cross Border Adjustment Mechanism – CBAM as well as EEX Global Carbon Index Core – GCI Core are fully available. 

OpenAPI is a widely adopted standard for describing APIs in a structured and consistent way. It defines how endpoints are organised, what parameters they accept, what responses they return, and how authentication is handled. This specification ensures that APIs are transparent, predictable, and easier to integrate across different systems and teams. 

Register on our new EEX Group DataSource Hub. By doing so, you will also be requested to sign up for a Deutsche Boerse Azure account. This step is needed to activate data access and choose your preferred multi factor authentication method. The email address to register must be the same as your EEX Group Webshop registration address. 

Due to security reasons, an API key is valid for one calendar year if an active data subscription is given.  

Every created API key has its own expiry date depending on the creation date. 

The user is responsible for API key creation and renewal before expiry. 

If the API key is missing, invalid, or expired, the API responds with the following generic error message: “401 – Authentication failed. Please verify your API token.” 

A user account can have up to 4 accesses in parallel. Therefore, 4 API keys can be created.  

Currently, the revamped REST API (v2) enforces a rate limit of one request per second per user. Each individual request can return up to 20,000 records. Access is subject to an active subscription and the use of a valid API key. 

All information including documentation as well as YAML files are available via EEX Group DataSource Hub.

A YAML file is the format typically used to write an OpenAPI specification. It is both human- and machine-readable, making it ideal for documenting API structures in a clear and accessible way. In our revamped REST API (v2), the YAML file provides a clear and structured definition of all available endpoints and fields, along with detailed descriptions to guide users. 

Please use our YAML files to create requests for access to data. Find more information on our EEX Group DataSource Hub.  

The revamped REST API (v2) supports both JSON and XML formats. This is aligned with the OpenAPI standard. 

It is technically not possible to provide CSV outputs with the revamped REST API (v2) and to respect the OpenAPI standard at the same time. Frequent client feedback provided evidence that sticking to a general API standard is the preferred principle although we understand it might be different in individual cases. 

If the CSV format remains a key element for data integration for specific reasons, you can try the following option to proceed: 

• The API responses can be converted to CSV files with appropriate programming language (e.g. Python). However, this means, some of the real-time character of the REST API gets lost.