IT Documentation by type

The TRF Conversion Parameters files provide the following data to the members on a daily basis:
■ Contract referential data: Contract code, Maturity, Number of days to expiry, Daily Settlement Price,etc.
■ Pricing of Funding leg and Dividend leg: Daily accrued funding, Daily accrued dividend, Accumulated funding, Accumulated dividend, etc.

This document sets out the file format specifications for Total Return Futures Conversion Parameters files and provides detailed field descriptions.

This document must be read by Euronext’s clients developing tools for retrieving and processing Market Data files.

Euronext’s UTP has a built-in protection mechanism that restricts the total number of messages (of all types) that a trading session can submit per second. In UTP-Derivatives, each session on the Common Customer Gateway (CCG) has a session limit of 100 msgs/s. Next to that, an inbound order throttle can be set at an individual contract level or for some contracts (product group). If the throttle for a contract is set to n messages per second, then the Trading Host will allow a maximum of n messages per second in a certain second for an ITM for that contract.

The purpose of this document is to set out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the binary format. More specifically, it describes the structures of the technical, administrative and market data messages and a precise definition for any field part of these message structures. Any message is composed by one header, one body, one trailer. The description of the CCG Derivatives protocol herein addresses all Euronext derivative-related trading engines.

This document sets out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the FIX 5.0 format. More specifically, it describes the structures of the technical, administrative and market data messages and a precise definition for any field part of these message structures. Any message is composed by one header, one body, one trailer. The description of the CCG Derivatives protocol herein addresses all derivative-related trading engines.

This document provides guidelines on how to write effective and efficient applications using the UTP protocols for Order Entry (Binary or FIX 5.0) and Market Data (XDP). It is important to be aware that this document is not a replacement for, but rather a complementary document to the UTP Reference Manuals (see related documentation below). Most of the points raised in this document are concerned with the most efficient, or Exchange friendly way of performing various tasks, and the Exchange requires application developers to adopt the recommendations given where relevant.

This document provides the list of errors that can be issued from the UTP Matching Engine upon receipt of request messages. Indeed, when the Matching Engine receives a request, it performs several checks on this incoming request message, and may reject it. When it does, the error is identified in the response message sent back by the Matching Engine by an error code together with an associated text in the Text [58] field.

Derivatives CCG Binary Header file - MiFID II

This document sets out the client messages specifications for Optiq® OEG using the SBE format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.  Please note that Euronext Block, and Algomi are not in scope of this document.

This document sets out the client messages specifications for Optiq OEG using the FIX 5.0 format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.

Note: Algomi is not in scope of this document.

Drop Copy is a service, providing near real-time copies of trade reports & order messages, usually used by for risk management, back-offices and compliance teams

Clients require a dedicated connection to receive Drop Copy messages, which can be setup with configuration that fits their needs.

The scope of data in Drop Copy could provide client messages for various (or all of their) Logical Accesses, for one, or across different Optiq Segments.

This version of the document covers activity on the Cash market only, that are in scope of Phase 2 of the migration to Optiq.

This document sets out the client messages specifications for Optiq® OEG using the SBE format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.

This document provides the list of errors that can be issued by the Optiq® Matching Engine upon reception of incoming private messages, occurrence of client or exchange business continuity conditions and also the errors that are issued by the Trade Reporting & Publication services.

This document provides the list of errors that can be issued by the Optiq® Matching Engine upon reception of incoming private messages, occurrence of client or exchange business continuity conditions and also the errors that are issued by the Trade Reporting & Publication services.

This document sets out the client messages specifications for TCS Optiq OEG using the SBE and FIX formats. 

This document sets out the client messages specifications for Optiq OEG using the FIX 5.0 format. More specifically, it describes the contents of administrative and application messages and provides detailed field descriptions.    Note: Euronext Block and Algomi are not in scope of this document.

This document details the Referential Data HTTPS Server for Euronext, to be used in conjunction with the Optiq MDG Client Specifications.

The Servers provide full referential data for the Euronext markets, as well as feed configurations and intraday trades with their MiFID II flags. Users of the Euronext market data feed should use the Servers to:

- Configure feed connections every day.

- Support the referential data that is disseminated on the feed.

- Complete their list of trades.

This document details the Referential Data HTTPS Server for Euronext, to be used in conjunction with the Optiq MDG Client Specifications.

The Servers provide full referential data for the Euronext markets, as well as feed configurations and intraday trades with their MiFID II flags. Users of the Euronext market data feed should use the Servers to:

- Configure feed connections every day.

- Support the referential data that is disseminated on the feed.

- Complete their list of trades.

This document describes the files generated on a daily basis by the Optiq for the End Of Day (EOD) application and provided to the members of the Euronext Cash regulated markets.

The purpose of this document is to describe all the specifications of Optiq™ Market Data Gateway.

The Euronext Optiq Market Data Gateway (MDG) provides high-speed, real-time market data for Euronext markets.

The data feed has the following high-level features:

■ Multicast technology

■ Ultra-low latency

■ MiFID II compliance

■ Cash & Derivatives message harmonization

■ Optimized feed for each type of connectivity

■ High availability

■ Reliable network solution

■ High level of scalability

■ Access to a wide range of European market data sets

This document provides detailed information about the features of the feed to support the development of client applications.

The Euronext Optiq Market Data Gateway (MDG) provides high-speed, real-time market data for Euronext markets.

The data feed has the following high-level features:

■ Multicast technology

■ Ultra-low latency

■ MiFID II compliance

■ Cash & Derivatives message harmonization

■ Optimized feed for each type of connectivity

■ High availability

■ Reliable network solution

■ High level of scalability

■ Access to a wide range of European market data sets

This document provides detailed information about the features of the feed to support the development of client applications.

The purpose of this document is to describe all the specifications of Optiq™ Market Data Gateway

The purpose of this document is to describe all the technical and application messages (APA and Euronext Synapse) of Market Data Gateway (MDG) i.e. Technical messages (Start of day, End of day and Health Status), Referential messages (for quotes and for trades), application messages (APA quotes and APA full trade information) and Snapshot messages and all the related features for those messages i.e. Snapshots (message recovery), Compression (market data packet for low bandwidth connections), Shaping (bandwidth optimization), Gap detection (packet loss recovery), System failures trade, Quote retransmission (outbounded messages rebroadcasting) and Health status Production timetable (list of events during the trading day).

This specification document is related to the Euronext Saturn Web Services, part of Euronext’s Reporting Services. Saturn offers a REST API which is used to access the services of the gateway. The purpose of this document is to describe the technology and the supported messages.

This document provides an overview of the exchange of messages between the Optiq Order Entry Gateway (OEG), the clients’ systems and the Market Data Gateway (MDG). It includes:

■ Typical trading scenarios and the corresponding public and private messages for these scenarios, and the different cases they may cover;

■ The names and IDs of the messages sent;

■ The events that trigger the transmission of messages.

This overview is meant to provide a description of the main structures and concepts used within this document, to facilitate the review of the individual topics and cases covered within.

The messages that are sent between trading members and Optiq are referred to as private messages whereas the messages that are sent by the external broadcasting systems are referred to as public messages.

Private messages are exchanged exclusively between the clients’ system and the Optiq matching engine via order entry gateways, for example to request information from the system or to issue a command (e.g., enter an order). Private messages are also sent back by Optiq via order entry gateways (OEGs) to the client’s system to provide the information requested, or confirm that a command has been successfully executed (or not), as well as to notify of trades, etc.

Public messages are sent by Optiq via MDG to provide to all subscribing clients with anonymized Market data, such as orders entered, best limits, trades executed, market events, updated limits, etc.

The diagrams in this document express representative examples of message sequences and other scenarios can be figured out from the ones described inside that document. The details of the message contents may vary depending on the example.

The diagrams also endeavour to represent as close to reality as possible the sequence in which events and steps occur, and messages are sent. This introduction provides indication when such cases are not feasible to represent faithfully due to complexity of graphical representation.

For a complete description of the messages and their fields, please refer to the associated document:

■ Optiq Order Entry Gateway Messages Specifications SBE;

■ Optiq Order Entry Gateway Messages Specifications FIX;

■ Optiq Market Data Gateway Messages Specifications.

This document provides an overview of the exchange of messages between the Optiq Order Entry Gateway (OEG), the clients’ systems and the Market Data Gateway (MDG). It includes:

■ Typical trading scenarios and the corresponding public and private messages for these scenarios, and the different cases they may cover;

■ The names and IDs of the messages sent;

■ The events that trigger the transmission of messages.

This overview is meant to provide a description of the main structures and concepts used within this document, to facilitate the review of the individual topics and cases covered within.

The messages that are sent between trading members and Optiq are referred to as private messages whereas the messages that are sent by the external broadcasting systems are referred to as public messages.

Private messages are exchanged exclusively between the clients’ system and the Optiq matching engine via order entry gateways, for example to request information from the system or to issue a command (e.g., enter an order). Private messages are also sent back by Optiq via order entry gateways (OEGs) to the client’s system to provide the information requested, or confirm that a command has been successfully executed (or not), as well as to notify of trades, etc.

Public messages are sent by Optiq via MDG to provide to all subscribing clients with anonymized Market data, such as orders entered, best limits, trades executed, market events, updated limits, etc.

The diagrams in this document express representative examples of message sequences and other scenarios can be figured out from the ones described inside that document. The details of the message contents may vary depending on the example.

The diagrams also endeavour to represent as close to reality as possible the sequence in which events and steps occur, and messages are sent. This introduction provides indication when such cases are not feasible to represent faithfully due to complexity of graphical representation.

For a complete description of the messages and their fields, please refer to the associated document:

■ Optiq Order Entry Gateway Messages Specifications SBE;

■ Optiq Order Entry Gateway Messages Specifications FIX;

■ Optiq Market Data Gateway Messages Specifications.

Euronext has developed a suite of reporting services to support the implementation of MiFID II. These services will be operated via a new tool named Saturn, which is composed of a Web API and a Webbased User Interface (UI) offering a number of features to clients. This document describes how to use the Saturn User Interface (UI) as a support of the global reporting services provided by Euronext.

Please note that this version of the User Guide covers the Transaction Reporting, ARM functional services as well as Admin features and Off Book On Exchange (OBOE) services..

This document sets out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the FIX 5.0 SP2 format. More specifically, it describes the structures of the technical, administrative and application messages for the CCG Euronext RiskGuard (ERG) Functionality. The description of the CCG Derivatives protocol herein addresses all Euronext derivative-related trading engines.

Euronext RiskGuard is a pre-trade risk management service providing Risk Managers at Clearing or Trading Member firms of Euronext the ability to monitor their clients' or firm's risk exposure. This document describes how to set and amend the different pre trade risk controls available through the Euronext RiskGuard web-based User Interface (UI).

This version of the User Guide is dedicated to Trading Member firms acting as ‘RiskGuard Members’. It provides a description of all the risk controls and additional features available through the RiskGuard User Interface to monitor their firm’s and client’s risk.

Euronext RiskGuard is a pre-trade risk management service providing Risk Managers at Clearing or Trading Member firms of Euronext the ability to monitor their clients' or firm's risk exposure. This document describes how to set and amend the different pre trade risk controls available through the Euronext RiskGuard web-based User Interface (UI).

This version of the User Guide is dedicated to clearing participants acting as ‘RiskGuard Clearers’. It provides a description of all the risk controls and additional features available through the RiskGuard User Interface to monitor their NCMs’ customers.

This document sets out the message specifications for the Common Customer Gateway for Derivative markets (CCG-D) using the FIX 5.0 SP2 format. More specifically, it describes the structures of the technical, administrative and application messages for the CCG Euronext RiskGuard (ERG) Functionality. The description of the CCG Derivatives protocol herein addresses all Euronext derivative-related trading engines.