EMS - FIX API
Financial Information eXchange (FIX) protocol is an electronic communications protocol initiated in 1992 for international real-time exchange of information related to securities transactions and markets.
You can use it for real-time order management and receiving execution reports from us, and it's an alternative to WebSocket protocol.
Implemented Standards:
Endpoints
Default session configuration:
[DEFAULT]
DefaultApplVerID=FIX.5.0
TransportDataDictionary=FIX/FIXT11.xml
AppDataDictionary=FIX/FIX50.xml
ConnectionType=initiator
ReconnectInterval=1
ResetOnLogon=Y
ResetOnLogout=Y
ResetOnDisconnect=Y
SenderCompID=OMS.FIX.CLIENT
SocketConnectPort=3401
SocketConnectHost=127.0.0.1
FIX 4.4session configuration:
[SESSION]
BeginString=FIX.4.4
StartTime=00:00:00
EndTime=00:00:00
TargetCompID=CoinAPI.OEML.FIX
DataDictionary=FIX/FIX44.xml
HeartBtInt=1
FileStorePath=store
FIX 5.0/FIXT 1.1session configuration:
[SESSION]
BeginString=FIXT.1.1
StartTime=00:00:00
EndTime=00:00:00
TargetCompID=CoinAPI.OEML.FIX
DataDictionary=FIX/FIX50.xml
HeartBtInt=1
FileStorePath=store| Deployment | Environment | Hostname | Port | Authentication |
|---|---|---|---|---|
| Managed Cloud | Production | Use Managed Cloud REST API /v1/locations to get specific endpoints to each server site where your deployments span | 3301 | TLS Client Certificate |
| Self Hosted | Production | IP Address of the ems-gateway container/excecutable in the closest server site to the caller location |
3401 | No |
Our sesssion configuration parameters:
| Parameter | Value |
|---|---|
| Hostname | look at the table above |
| Port | look at the table above |
| Specifications | *(XML FIX Specification can be downloaded here: FIX44.xml (opens in a new tab) |
| ) FIX50.xml (opens in a new tab) FIXT11.xml (opens in a new tab))* | |
| Gateway timezone | UTC |
| ReconnectInterval | 1 |
| ResetOnLogon | Y |
| ResetOnLogout | Y |
| ResetOnDisconnect | Y |
| SenderCompID | OMS.FIX.CLIENT |
| TargetCompID | CoinAPI.OEML.FIX |
| SocketConnectPort | look at the table above |
| StartTime | 00:00:00 |
| EndTime | 00:00:00 |
| HeartBtInt | 1 |
Authentication
As you can observe in the documentation below in the Logon FIX Message, do not contain any authentication data. This is by design.
If the software is deployed as Self-Hosted then API do not require authentication as inside your infrastructure, your company is responsible for the security and access controls.
If the software is deployed in our Managed Cloud, then we need your client to provide us the certificate from the Managed Cloud REST API, while establishing a TLS session with us. We are using the that client certificate provided on the TLS layer, to authenticaticate your FIX session.