Data

GraphQL  API migration

What is changing?

Main changes  

Users need to consider following changes between Version 1.1.0 (AWS) and 2.0.0 (GCP)  

  • Datatypes AWSDate and AWSTime are renamed to Date and Time.
  • GET Requests are no longer supported:
    • Although not documented, Version 1.1.0 supported GET requests with a URL encoded query in addition to POST requests.
    • In Version 2.0.0, only POST requests will be supported.
  • New URL for endpoint is https://api.developer.deutsche-boerse.com/eurex-prod-graphql/
  • Authentication method stays the same (API-Key/token).
  • All queries are still available.

When will it happen?

The new GCP endpoint with version 2.0.0 will be available starting 1 December 2025. Details can be found here: https://console.developer.deutsche-boerse.com/apis/50247b4e-dae5-4db7-be15-27bd5b17a082

A parallel run period is offered during which both the AWS and GCP endpoints are live and deliver identical data. The AWS endpoint with Version 1.1.0 will be decommissioned within the next 3-4 weeks. 

How can you test the new version?

  • A test instance of the GCP endpoint is already available.
  • Registration for the test endpoint is not required. Feel free to use the provided demo key for the connection.
  • Test endpoint: https://api.developer.dbp.simu.gcp.dbgservice.com/eurex-test-graphql/.
  • Key: { "X-DBP-APIKEY" : "fa5f182a-1d5c-44c1-a3a2-2b8392bee715" }
  • The test dataset mirrors the production schema, so you can run the same queries you use today.

What steps need to be done?

Step 1

Test your software against the new test endpoint, which is available today.

Step 2 (after 1 December)

Registered users can add in DBAG API portal the new endpoint to their application:

  • Sign In
  • Navigate to API Catalogue > Eurex-Data via GraphQL
  • Select 'Add to Application'
  • Select either the existing application, if you want to use the same API-Key as in AWS, or 'Create New' if you want to enforce separate Keys

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.


Support & contact

Feel free to ask if you need example queries against the test endpoint or help with updating your integration code.

Viktor Uvarov
Eurex Frankfurt AG | Trading Design

T +49-69-211-1 42 82
viktor.uvarov@eurex.com
 

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.