Eurex
With this Newsflash, we would like to draw your attention to the upcoming Reference data/GraphQL API migration.
1. Introduction
The Eurex GraphQL API will move from the current AWS-based production endpoint to a new GCP-based production endpoint.
2. Required action
Users need to consider the following changes between Versions 1.1.0 (AWS) and 2.0.0 (GCP):
3. Details of the migration
3.1 Timing
3.2 Testing
3.3 User Checklist
Action | |
Step 1 | Test your software against the new test endpoint, which is available today. |
Step 2 (after 1 December) | Registered users can add-in the DBAG API portal to the new endpoint to their application using the following steps:
|
Step 3 | Update your application/configuration to use the new GCP endpoint URL. |
Step 4 | Run your existing queries against the GCP endpoint during the parallel run to verify behavior. |
For further details please refer to the dedicated subsite available on our website under the following link: GraphQL API.
If you need example queries against the test endpoint or help with updating your integration code, feel free to contact Viktor Uvarov from Trading Design at tel. +49-69-211-1 42 82 or viktor.uvarov@eurex.com.
Kind regards,
Your Client Services Team

Visit now Eurex Support Trading to access a wide array of support content!
Recipients: | All Trading Participants of Eurex Deutschland and Vendors | |
Target groups: | Front Office/Trading, Middle + Backoffice, IT/System Administration, Auditing/Security Coordination | |
Contact: | Viktor Uvarov, Trading Design, tel. +49-69-211-1 42 82, viktor.uvarov@eurex.com | |
Web: | GraphQL API |
Market Status ⓘ
XEUR
The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.
Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message.
We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.