Introduction
Financial Information eXchange (FIX) protocol is an electronic communications protocol initiated in 1992 for international real-time exchange of information related to the securities transactions and markets. You can use it to receive real-time market data from us and it's an alternative to WebSocket protocol.
Market Data - FIX API
Financial Information eXchange (FIX) protocol is an electronic communications protocol initiated in 1992 for international real-time exchange of information related to the securities transactions and markets. You can use it to receive real-time market data from us and it's an alternative to WebSocket protocol.
[!NOTE]
If you don't have experience with FIX protocol, consider using a much simpler to implement REST or WebSocket API.
Implemented Standards:
Endpoints
| Enviroment | Encryption | Value | Region |
|---|---|---|---|
| Production | Yes | fix.coinapi.io:3303 | GeoDNS (auto-routing) |
| Production | No | fix.coinapi.io:3302 | GeoDNS (auto-routing) |
| Production | Yes | api-ncsa.coinapi.io:3303 | North & South America |
| Production | No | api-ncsa.coinapi.io:3302 | North & South America |
| Production | Yes | api-emea.coinapi.io:3303 | Europe, Middle East & Africa |
| Production | No | api-emea.coinapi.io:3302 | Europe, Middle East & Africa |
| Production | Yes | api-apac.coinapi.io:3303 | Asia Pacific |
| Production | No | api-apac.coinapi.io:3302 | Asia Pacific |
[!NOTE]
The default endpoints (
fix.coinapi.io) use GeoDNS to automatically route your connections to the nearest datacenter. If you prefer to use a specific region, you can use the region-specific endpoints listed above.
FIX client configuration file for encrypted connection:
[DEFAULT]
ConnectionType=initiator
ReconnectInterval=2
FileStorePath=store
FileLogPath=log
StartTime=00:00:00
EndTime=00:00:00
NonStopSession=Y
UseDataDictionary=Y
ValidateFieldsOutOfOrder=N
DataDictionary=FIX44.xml
SocketConnectHost=fix.coinapi.io
SocketConnectPort=3303
SSLEnable=Y
SSLServerName=fix.coinapi.io
SSLValidateCertificates=Y
SSLCheckCertificateRevocation=Y
LogoutTimeout=5
ResetOnLogon=Y
ResetOnLogout=Y
ResetOnDisconnect=Y
[SESSION]
BeginString=FIX.4.4
SenderCompID=YOUR_API_KEY
TargetCompID=COINAPI_V2
HeartBtInt=10FIX client configuration file for unencrypted connection:
[DEFAULT]
ConnectionType=initiator
ReconnectInterval=2
FileStorePath=store
FileLogPath=log
StartTime=00:00:00
EndTime=00:00:00
NonStopSession=Y
UseDataDictionary=Y
ValidateFieldsOutOfOrder=N
DataDictionary=FIX44.xml
SocketConnectHost=fix.coinapi.io
SocketConnectPort=3302
SSLEnable=N
LogoutTimeout=5
ResetOnLogon=Y
ResetOnLogout=Y
ResetOnDisconnect=Y
[SESSION]
BeginString=FIX.4.4
SenderCompID=YOUR_API_KEY
TargetCompID=COINAPI_V2
HeartBtInt=10Our production endpoint configuration parameters:
| Parameter | Value |
|---|---|
| Protocol version | FIX.4.4 (XML FIX Specification can be downloaded here: FIX44.xml) |
| Gateway timezone | UTC |
We recommend using our SDK or listed client libraries depending on your language requirements:
Security
Stunnel configuation:
[COINAPI]
client = yes
accept = 3302
connect = fix.coinapi.io:3303
verify = 2Communication with our FIX gateway is secured by TLS protocol if you are using the encrypted port. If your FIX protocol implementation does not support establishing a connection over a secure channel, you must use a proxy between your client and our FIX gateway to unbundle encryption or use the unencrypted port. We recommend stunnel as a proxy if a secure connection can't be established directly from your client and you can't allow unencrypted traffic.
[!TIP]
You should assume that we are always providing certificates signed by the Trusted Certification Authority.
oneZero Hub
Our FIX Connector is passing oneZero Conformance Test. If you need to establish a session using the FIX with your company oneZero Hub, please contact our support at CoinAPI Support.
Messages
WebSocket endpoint provides real-time market data streaming which works in Subscribe-Publish communication model. After establishing a WebSocket connection with us, you will need to send a Hello message documented below.
Messages
All FIX messages are equipped with Standard Header and Trailer, below we will describe what is required in them in accordance with FIX 4.4, the standard that we use.