Product specification

This section contains the product specification of the Infront Data Manager API - Streaming.

Infront Data Manager API - Streaming provides a subscription-based API for receiving price updates of listings in a continuous data stream. Real-time data ideal for immediate updates like stock tickers and live analytics.
The API provides remote procedure calls to login and logout, to subscribe and unsubscribe, and to start receiving the data stream.
Infront Data Manager API - Streaming is a B2B solution that offers client libraries in Java and .NET for accessing streaming data and a subset of reference data. It is designed to succeed multiple existing B2B systems within Infront.
How to access: Customers are registered in Infront systems through manual process, which generate username/password combinations and/or client credentials. These credentials are utilized within Java/.NET client libraries to connect to a publicly accessible URL, such as: http://dml.cloud.eu.infrontservices.com/

To access our data, user need to have the appropriate entitlements, which are established through formal agreements with us and or data providers (like exchanges). Once these agreements are in place or arrangements are made to get them signed, the necessary credentials will be handed out. This process is handled by Infront Business and Procurement team.

User will be provided credentials and URLs in a configuration file with our Java (version 11 or higher) or C# (.NET Core 6 or higher) client libraries to securely connect to our testing and production servers. These client libraries automatically manage authentication, retries, and other necessary abstractions, simplifying the integration process. Additionally, the client libraries come with comprehensive documentation and examples to help the user connect to both streaming and static/reference data sets.

User need to ensure that specific URLs, such as those for our authentication systems and data streaming servers, are allowed through the data center’s network configurations. While newer cloud-native setups typically do not have restrictions, older on-premises environments may still use outgoing IP filtering that requires adjustment.
Some example URLs are *.cloud-uat.eu.infrontservices.com and *cloud.eu.infrontservices.com

Our services are accessible over the public internet. You will connect to our front-end data centres using the URLs.

We use TCP/IP with SSL termination over port 443 to secure communications. The underlying protocol is HTTP/2, which is used for gRPC. For optimal performance and reliability, we recommend establishing a direct connection and avoiding the use of any HTTP proxies.