Crypto FIX API — How It Works and Which Exchanges Support It

TL;DR — A crypto FIX API lets a trading firm send orders and receive market data over the Financial Information eXchange (FIX) protocol — the same session-based, tag-value messaging standard used in equities and FX — instead of a REST or WebSocket API. Among major crypto venues, Coinbase, Kraken, Gemini, Binance, Crypto.com, and CEX.IO offer native FIX order entry; most FIX deployments in crypto run on FIX 4.4 (Coinbase Exchange also runs a FIX 5.0 gateway). Many large venues — including OKX, Bybit, and KuCoin — expose only REST and WebSocket natively. Firms that want one FIX session across many exchanges use an aggregation/normalization layer that presents every venue behind a single FIX endpoint.

What is a FIX API?

FIX (Financial Information eXchange) is an open, vendor-neutral messaging standard for electronic trading. It was initiated in 1992 by a group of institutions and brokers to replace phone-and-fax order handling with structured electronic messages, and it is maintained by the FIX Trading Community, a non-profit, industry-driven standards body. FIX is used across equities, fixed income, FX, and derivatives — by banks, prime brokers, asset managers, and exchanges from NYSE to CME — and it is now also offered by a growing set of crypto exchanges for institutional connectivity.

A FIX message is a sequence of tag=value pairs separated by a control character (ASCII SOH, 0x01). Each numeric tag has a defined meaning. In an order message, tag 35 is the message type, 55 is the symbol, 54 is the side, 38 is the quantity, 40 is the order type, and 44 is the price. A real Kraken spot order looks like this (SOH shown as |):

8=FIX.4.4|35=D|49=MYCOMPID|56=KRAKEN-TRD|11=1688738168|38=0.01|40=2|44=1000|54=1|55=BTC/USD|59=1|60=20230707-13:56:08.277|10=222|

That single line is a FIX 4.4 New Order Single (35=D) to buy (54=1) 0.01 (38) BTC/USD (55) as a limit order (40=2) at 1000 (44), good-till-cancel (59=1).

FIX message types you will actually use

FIX vs REST vs WebSocket — the key differences

Almost every crypto exchange exposes a REST API (request/response over HTTP) and a WebSocket API (a persistent push stream). FIX differs from both in ways that matter to institutional and high-frequency traders.

Session-based with guaranteed sequencing. A FIX session assigns every message a sequence number and supports resend requests and gap-fill, so a client can detect and recover missed messages after a disconnect rather than silently losing fills. This recoverable, in-order session layer is the core of the standard and is what REST polling and raw WebSocket streams do not provide out of the box.

An industry standard, not a per-venue dialect. A firm already running a FIX engine for equities or FX reuses the same infrastructure, order semantics, and reconciliation logic. REST and WebSocket schemas are designed per exchange, so every integration is bespoke.

Lean, fast messages. FIX tag-value (and binary FIX/SBE) messages are smaller than JSON payloads — exchanges that have published comparisons cite roughly 30% smaller messages than REST/WebSocket JSON — which, combined with co-located direct market access (DMA), supports microsecond-class latency for HFT.

Clean separation of concerns. Most crypto FIX implementations run trading and market data as separate sessions, often with a third drop copy session that receives execution reports read-only for risk and middle-office systems.

The trade-off: FIX is heavier to implement than a REST call, demands dedicated infrastructure, and is typically gated behind institutional onboarding, IP whitelisting, and an account manager. REST and WebSocket are open to any account and are simpler for building UIs, bots, and lower-frequency strategies. The three are complementary — many firms trade over FIX while building their dashboards on REST/WebSocket.

Which crypto exchanges support FIX natively

"Native" below means the exchange operates its own FIX gateway; it does not count third-party FIX bridges.

Notes on the native-FIX venues

• Coinbase Exchange documents a legacy FIX 4.2 order-entry gateway and a newer FIX 5.0 order-entry gateway; the 4.2 order-entry gateway was scheduled for deprecation in June 2025, with FIX 5.0 recommended. FIX 5.0 uses begin string 8=FIXT.1.1 with the application version in DefaultAppVerID (tag 1137=9), and the gateway keeps a 4-hour message replay history. Coinbase Derivatives runs a separate FIX 4.4 order-entry API.
• Kraken offers a FIX 4.4 API for institutional and HFT clients covering both Spot and a separate Derivatives engine, accessed via separate sessions and CompIDs (the derivatives SenderCompID carries a DRV suffix). It provides deterministic message ordering, session-based Cancel-on-Disconnect (CoD / "kill switch"), sequence-number message replay, L3 order book data, and TLS 1.3. Kraken states its spot FIX API carries billions of dollars in volume per month.
• Gemini supports FIX 4.4 for order entry. When a FIX session disconnects, Gemini cancels all orders associated with that session.
• Binance launched a FIX API for Spot in August 2024, with three session types — order entry, market data, and drop copy. It is Spot-only, uses Ed25519 API keys over TLS, requires the FIX_API permission (FIX_API_READ_ONLY for read-only/drop copy), delays drop-copy data by ~1 second, and supports order lists (OCO, OTO, OTOCO). Binance Futures does not expose FIX.
• Crypto.com introduced a FIX 4.4 API on its GEN 3.0 exchange for institutional DMA, including read-only drop copy and incremental order book feeds.
• CEX.IO exposes a FIX API aimed at institutional clients alongside REST and WebSocket.

A venue's symbol format is its own choice and is not part of the FIX standard: the same Bitcoin/USD pair is BTC-USD on Coinbase, BTC/USD on Kraken spot, and BTCUSD on Gemini; Ether/Tether is BTCUSDT-style concatenation on Binance and Bybit but BTC-USDT on OKX and KuCoin. This per-venue symbology divergence is one of the main integration costs when connecting to multiple exchanges, FIX or not.

What you can do over a crypto FIX session

The common workflow across crypto FIX venues mirrors standard FIX order handling:

• New Order Single (35=D) — submit an order; order type in tag 40 (1=market, 2=limit, 3=stop, 4=stop-limit), side in 54 (1=buy, 2=sell), quantity in 38, price in 44, time-in-force in 59 (GTC, IOC, FOK).
• Order Cancel Request (35=F) and Cancel/Replace (35=G) — cancel or amend working orders, referenced by ClOrdID (tag 11).
• Order Mass Cancel Request (35=q) — cancel many orders at once; a protocol-level kill switch.
• Execution Report (35=8) — the server's response carrying order status in tag 39 and execution type in 150 (new, partial fill, fill, canceled, replaced, rejected).
• Market Data Request (35=V) — subscribe to order book and trade streams, answered by snapshot and incremental refresh messages.
• Security List (35=y) — receive reference data: the set of tradable instruments and their identifiers.

Session management uses the standard FIX administrative messages — Logon (35=A), Heartbeat (35=0), Test Request, Resend Request, Sequence Reset/Gap-Fill, and Logout (35=5) — and risk controls such as Cancel-on-Disconnect and self-trade prevention (STP).

Why use FIX for crypto trading at all

FIX makes the most sense for firms that already think in FIX — proprietary trading firms, market makers, hedge funds, and platforms with an existing FIX engine and OMS/EMS. For them, adding a crypto venue that speaks FIX is closer to a configuration change than a new integration, and the session-recovery guarantees, deterministic ordering, and standardized order semantics are exactly what automated and high-frequency strategies depend on.

The limitation is coverage: native FIX exists at only a handful of venues, and where it does exist, symbol formats, supported order types, session rules, and authentication differ exchange to exchange. A firm wanting FIX access to venues that only speak REST/WebSocket — or wanting one consistent FIX dialect and one normalized symbology across all of them — needs a normalization layer.

How Axon Trade fits in

This section describes Axon Trade's own product; everything above is vendor-neutral.

Axon Trade is an institutional-grade OEMS (Order and Execution Management System) for digital asset trading that exposes a single, slightly modified FIX 4.4 API connecting to 30+ exchanges through one session — including venues that offer native FIX (Coinbase, Kraken, Gemini, Binance) and venues that do not (OKX, Bybit, and others), which Axon bridges behind the same FIX endpoint.

Two things make this practical across so many venues:

• Normalized symbology. Axon maintains a normalized symbol and asset database, so the same canonical symbol — for example ETH/USDT in slash form — is used identically for market data and execution across every connected exchange, regardless of each venue's native format. Reference data is delivered via the FIX SecurityList message (35=y) carrying Symbol (55) and SecurityExchange (207). [Axon: confirm current normalized-symbol count before citing a figure.]
• Managed connectivity and low added latency. Axon runs inside Equinix data centers with software-added latency of about 35 microseconds, offers cross-connect and co-location, and handles each exchange's protocol updates so clients do not have to.

As an active member of the FIX Trading Community, Axon treats this normalization as a stopgap pending a formal ISO crypto-naming standard.

FAQ

What is a crypto FIX API?
It is an interface that lets a firm trade on a crypto exchange using the Financial Information eXchange protocol, a session-based tag-value messaging standard from traditional finance, instead of a REST or WebSocket API.

Which crypto exchanges support FIX?
Among major venues, Coinbase, Kraken, Gemini, Binance, Crypto.com, and CEX.IO offer native FIX. Coinbase runs FIX 4.2 and 5.0 gateways; Kraken, Gemini, Binance, and Crypto.com run FIX 4.4. Binance FIX is Spot-only.

Does Binance have a FIX API?
Yes. Binance launched a FIX API for Spot trading in August 2024, covering order entry, market data, and drop copy. It runs on FIX 4.4 and requires an Ed25519 API key. Binance Futures does not offer FIX.

Does OKX have a FIX API?
OKX native API is REST and WebSocket; it does not document a native FIX gateway for general order entry. Firms that want FIX access to OKX typically use an aggregation layer that presents OKX behind a FIX endpoint.

Does Kraken have a FIX API?
Yes. Kraken offers a FIX 4.4 API for institutional and HFT clients, covering both Spot and Derivatives via separate sessions, with Cancel-on-Disconnect and sequence-based message replay.

What FIX version do crypto exchanges use?
FIX 4.4 is the most common in crypto. Coinbase Exchange additionally offers a FIX 5.0 order-entry gateway. FIX 4.2 and 4.4 remain officially supported by the FIX Trading Community.

FIX API vs REST API for crypto — which is better?
Neither is universally better. FIX suits firms with existing FIX infrastructure that need low latency, session recovery, and standardized order semantics; REST and WebSocket are simpler, open to any account, and available on every venue. Many large exchanges offer only REST and WebSocket.

FIX vs WebSocket — what is the difference?
WebSocket is a general-purpose, full-duplex web protocol good for streaming market data to many clients. FIX is a financial-industry standard with a recoverable session layer, sequence numbers, and standardized order messages, built for order execution and reconciliation.

What is a drop copy session?
A read-only FIX session that receives copies of execution reports for an account, used by risk, compliance, and middle-office systems to monitor order activity without being able to place or cancel orders.

Sources

• FIX Trading Community — FIX Protocol overview and supported versions: https://fixtrading.org/standards/fix-protocol/
• FIX Trading Community — Introduction / history (initiated 1992): https://www.fixtrading.org/online-specification/introduction/
• Coinbase — Exchange API welcome (FIX order entry, FIX 4.2 deprecation, FIX 5.0): https://docs.cdp.coinbase.com/exchange/docs/welcome
• Coinbase — FIX 5.0 order entry messages (FIXT.1.1, tag 1137, 4-hour replay): https://docs.cdp.coinbase.com/exchange/docs/fix-msg-order-entry-50
• Coinbase — Derivatives FIX order entry (FIX 4.4): https://docs.cloud.coinbase.com/derivatives/docs/fix-msg-order
• Kraken — FIX API introduction (FIX 4.4, spot + derivatives, CoD, TLS 1.3, replay): https://docs.kraken.com/api/docs/guides/fix-intro
• Kraken — FIX authentication (separate Spot/Derivatives sessions, DRV CompID): https://docs.kraken.com/api/docs/guides/fix-auth/
• Kraken — New Order Single (FIX 4.4 example messages): https://docs.kraken.com/api/docs/fix-api/nos-fix/
• Gemini — FIX Order Entry API reference (FIX 4.4 only): https://docs.gemini.com/fix-api/
• Binance — Spot API Service Upgrade announcement (FIX API launch, 2024-08-08): https://www.binance.com/en/support/announcement/binance-spot-api-service-upgrade-2024-08-08-0301491cff254832ba07ef78b04fe6b2
• Binance — FIX API documentation (Ed25519, order/market-data/drop-copy sessions): https://developers.binance.com/docs/binance-spot-api-docs/fix-api
• Crypto.com — Introducing FIX API for the GEN 3.0 Exchange (FIX 4.4, DMA, drop copy): https://crypto.com/en/product-news/fixapi
• OKX — API guide (REST / WebSocket): https://www.okx.com/docs-v5/en/
• Bybit — V5 API documentation (REST / WebSocket): https://bybit-exchange.github.io/docs/v5/intro
• KuCoin — API documentation (REST / WebSocket): https://www.kucoin.com/docs-new/
• CoinAPI — FIX API vs REST API comparison: https://www.coinapi.io/blog/fix-api-vs-rest-api
• Axon Trade — home and supported exchanges (30+, ~35µs added latency, single FIX session): https://axon.trade/ and https://axon.trade/supported-exchanges
• Axon Trade — FIX & REST API documentation (slightly modified FIX 4.4): https://docs.axon.trade/

Facts verified against primary sources as of June 2026. FIX version support, exchange API offerings, session rules, and symbol formats change; re-check the linked venue docs before reuse.