Which Crypto Exchanges Support FIX

TL;DR

As of 2026, the major crypto exchanges with a documented, first-party FIX API are Binance (Spot), Coinbase (International, Exchange, and Prime), Kraken, Gemini, Deribit, Crypto.com, Bitstamp, and CEX.IO. Most run FIX 4.4, but the picture is mixed: Coinbase International uses FIX 5.0, Coinbase Exchange splits order entry (FIX 4.2) from market data (FIX 5.0), and Coinbase Prime's baseline is FIX 4.2 with a FIX 5.0 API in beta. OKX and Bybit do not publish public FIX API documentation; their developer docs describe REST and WebSocket only. Bitfinex offers FIX through an open-source gateway rather than a native endpoint.

What "FIX support" means at a crypto exchange

FIX (Financial Information eXchange) is the messaging standard institutional trading systems have used since the 1990s for order routing and market data. When a crypto exchange says it "supports FIX," that support typically breaks down into up to three distinct session types, each with its own endpoint and permissions:

• Order entry — placing, amending, and canceling orders; receiving ExecutionReport (35=8) messages. Every FIX-supporting venue offers this.
• Drop copy — a read-only stream of the account's execution reports, used for real-time risk, compliance, and reconciliation, typically on separate read-only credentials. Offered by Binance, Coinbase International, Gemini, and Crypto.com, among others.
• Market data — order book snapshots and incremental updates (35=W / 35=X) over FIX. Offered by Binance, Coinbase International, Coinbase Exchange, Kraken, Gemini, and Deribit.

Not every venue offers all three: Coinbase Prime's FIX API baseline, for example, covers order entry (FIX 4.2).

Which crypto exchanges support FIX — comparison table

Exchange-by-exchange detail

Binance (Spot)

Binance offers a FIX API for its Spot exchange only — the docs state it "can only be used with the SPOT Exchange." It provides three session types on separate endpoints: Order Entry (fix-oe.binance.com:9000), Drop Copy (fix-dc.binance.com:9000), and Market Data (fix-md.binance.com:9000), all over TCP+TLS. The protocol version is FIX 4.4. Two details stand out. First, FIX sessions only support Ed25519 API keys — the Logon signature is an Ed25519 signature over a defined field payload, a departure from the HMAC schemes common elsewhere. Second, resend requests are not supported: recovery relies on reconnecting rather than FIX-level message retransmission. Drop Copy data is delayed by 1 second. Order-entry sessions carry a limit of 10,000 messages per 10 seconds.

Coinbase International (INTX)

Coinbase International Exchange — Coinbase's non-US derivatives and spot venue — runs a FIX API with a baseline of FIX 5.0. It exposes three production endpoints over TCP+SSL: Order Entry (port 6110), Market Data (6120), and Drop Copy (6130). Resend requests are not supported; every connection is a new session with fresh sequence numbers, and the exchange resets sequences weekly (Saturday 12:00 CDT, or on Logon with ResetSeqNumFlag=Y).

Coinbase Exchange

Coinbase Exchange (the central limit order book behind Coinbase's institutional spot trading) has a mixed FIX baseline: order entry on FIX 4.2 SP2 and market data on FIX 5.0 SP2. The legacy FIX 4.2 order-entry gateway was deprecated on June 3, 2025, with Coinbase directing clients to the newer FIX 5 order-entry gateway. Logon authentication uses an HMAC signature over a defined prehash string (SendingTime, MsgType, MsgSeqNum, SenderCompID, TargetCompID, Password). Resend requests are not supported.

Coinbase Prime

Coinbase Prime — the prime brokerage product — uses FIX 4.2 as its order-entry baseline, with a FIX 5.0 API in beta. Unlike the exchange-level APIs, Prime supports message replay and sequence-number renegotiation per the FIX session layer, plus a separate queuing mechanism that holds a rolling 24 hours of messages for inactive sessions. Sessions are forcibly logged out daily during a 5:00–5:05pm ET maintenance window, after which sequence numbers reset to 1. Limits: up to 7 concurrent FIX sessions per portfolio, 1 session per API key, 50 messages/second per session.

Kraken

Kraken's FIX API is a FIX 4.4 implementation aimed at institutional and HFT clients, positioned by Kraken as its lowest-latency order-entry path. A single Spot FIX API Key covers both Spot and Derivatives markets, with orders routed to the appropriate trading engine per instrument. Distinctive session mechanics: cancel-on-disconnect (configured at onboarding), standard sequence-number-based replay of ExecutionReports, a daily logical rollover at 22:00 UTC, mandatory TLS 1.3, and IP whitelisting before logon. Dedicated ports separate Spot/Derivatives trading and L2/L3 market data (ports 4000–4005).

Gemini

Gemini supports FIX 4.4 only — its connectivity guide states plainly that "Gemini currently only supports FIX 4.4." It offers Order Entry, Market Data, and Drop Copy FIX sessions. The most distinctive fact is the connectivity model: Gemini lists three options for production FIX access — a cross-connect at its point of presence in Equinix NY5 (Secaucus, New Jersey), reachable from NY2/NY4/NY5 infrastructure, an approved extranet provider, or a third-party OMS. A public-internet FIX endpoint is not among them; when announcing the API, Gemini stated that its security and engineering teams considered FIX over the public internet an awkward and potentially insecure use of the protocol.

Deribit

Deribit — a derivatives-focused venue — implements a subset of FIX 4.4, extended with some tags from FIX 5.0 and several custom tags. Reflecting that focus, the message catalog goes beyond plain order entry: position reports (AN/AP), Market Maker Protection (custom MM/MR/MZ messages), mass quoting (i/b/Z), and trade capture reports. Resend Request (35=2) is part of the supported session-message set. TargetCompID is the constant DERIBITSERVER; endpoints offer both raw TCP (9881) and SSL (9883).

Crypto.com

Crypto.com introduced a FIX 4.4 API alongside its GEN 3.0 Exchange, announced in March 2026, positioning it explicitly for institutional direct market access. Features named in the announcement: read-only drop-copy sessions on separate keys, incremental order-book update feeds, native sub-account support for strategy/risk segregation, mass order create/cancel, OTC block trading over FIX, and in-order guaranteed delivery with ResendRequest-based recovery. Connectivity is via co-location in AWS Tokyo.

Bitstamp

Bitstamp has offered FIX connectivity to professional and institutional clients since 2017 — by its own account, it was one of the first crypto exchanges to do so — and replaced its original FIX solution with a redesigned in-house FIX interface in late 2022, with support for the old one ceasing on January 1, 2023. Bitstamp's API page lists FIX alongside its HTTP and WebSocket APIs.

CEX.IO

CEX.IO supports FIX protocol version 4.4 and offers its FIX API exclusively to institutional traders, with access granted on request via support. Beyond the protocol version and institutional-only gating, its public page does not break down session types or endpoints.

Bitfinex — FIX via gateway, not a native endpoint

Bitfinex is a special case: it does not operate a venue-managed FIX endpoint the way the exchanges above do. Its published FIX path is bfxfixgw, an open-source FIX gateway in Bitfinex's official GitHub organization, developed with Connamara, which accepts FIX 4.2 sessions and translates them to Bitfinex's WebSocket API. The gateway runs in order-routing mode, market-data mode, or both. Because the gateway is self-hosted, it is deployed and operated by the client — session management runs on the client's side rather than the venue's.

Which major venues do not offer native FIX

Native FIX is far from universal among top venues. As of July 2026, the public developer documentation of OKX and Bybit describes REST and WebSocket APIs, with no public FIX API documentation. Firms whose stack is built on FIX can reach such venues through third-party infrastructure that exposes a FIX interface and handles the native-protocol translation behind it.

This absence is one half of the fragmentation story. The other half is that even the venues that do offer FIX offer it differently.

Same protocol, different dialects — what actually differs

"Supports FIX" compresses a lot of variance. Concretely, across the venues documented above:

Versions span three generations. FIX 4.2 (Coinbase Exchange order entry, Coinbase Prime, the Bitfinex gateway), FIX 4.4 (Binance, Kraken, Gemini, Deribit, Crypto.com, CEX.IO), and FIX 5.0 (Coinbase International, Coinbase Exchange market data, Coinbase Prime beta).

Authentication is venue-specific. Binance requires an Ed25519 signature in the Logon message and accepts only Ed25519 API keys. Coinbase Exchange signs Logon with an HMAC over a defined prehash string. Deribit authenticates with a client secret from the account's API settings. Kraken requires IP whitelisting and assigns CompIDs at onboarding.

Recovery semantics diverge. Binance, Coinbase International, and Coinbase Exchange do not support resend requests — a disconnect means a new session and fresh sequence numbers. Kraken, Coinbase Prime, Deribit, and Crypto.com do support FIX-level replay or resend. For an OMS, these are two different recovery models to implement.

Connectivity models differ. Most venues terminate FIX over TCP+TLS on the public internet; Gemini's production options are a data-center cross-connect, extranet, or third-party OMS; Crypto.com and Kraken advertise co-location options (AWS Tokyo; Kraken's colocation program).

Scope differs. Binance's FIX covers Spot only; Kraken's covers Spot and Derivatives through one key; Deribit's is a derivatives API with market-maker machinery (MMP, mass quotes) that spot venues don't expose.

And the target moves. Coinbase deprecated its FIX 4.2 order-entry gateway in mid-2025 in favor of FIX 5; Bitstamp replaced its entire FIX stack in 2022–2023; Crypto.com's FIX API only launched with its GEN 3.0 exchange in 2026.

Is there a crypto FIX standard?

Not yet — but standardization work exists. The FIX Trading Community, the non-profit body that owns and maintains the FIX Protocol, runs a Digital Asset Working Group focused on the use of FIX for electronic trading of digital assets, and its co-chairs participate in ISO TC68/SC8/WG3 on related standards. The community's position is that "very little in the FIX Protocol actually needs to change to support digital assets" — the gap is in adoption and consistent practice across venues, not in the protocol's expressiveness. In the meantime, versions, authentication, and session rules differ venue by venue, and the differences catalogued above are the practical reality an integrator faces.

How Axon Trade fits in

Axon Trade is an institutional-grade OEMS for digital asset trading that approaches this fragmentation from the other side: instead of one FIX integration per venue, a client connects through a single, slightly modified FIX 4.4 session that reaches 30+ exchanges. For venues that offer no native FIX API, Axon Trade can build connectors, so FIX-based access is not limited to the exchanges that host FIX themselves. Symbols are normalized to one canonical slash format (e.g. ETH/USDT), identical for market data and execution across venues. Normalized reference data is delivered over FIX via SecurityList (35=y) with Symbol (55) and SecurityExchange (207). Axon Trade is a member of the FIX Trading Community.

FAQ

Which crypto exchanges support FIX API? Binance (Spot), Coinbase International, Coinbase Exchange, Coinbase Prime, Kraken, Gemini, Deribit, Crypto.com, Bitstamp, and CEX.IO document first-party FIX APIs. Bitfinex offers FIX through an open-source gateway. OKX and Bybit publish REST and WebSocket documentation without a public FIX API.

What FIX version do crypto exchanges use? Most use FIX 4.4 — Binance, Kraken, Gemini, Deribit, Crypto.com, and CEX.IO. Coinbase International uses FIX 5.0, while Coinbase Exchange and Coinbase Prime have FIX 4.2 baselines with FIX 5.0 gateways rolled out or in beta.

Does Binance have a FIX API? Yes — for the Spot exchange only, with separate order entry, drop copy, and market data sessions on FIX 4.4, and it requires Ed25519 API keys.

Does Coinbase use FIX 4.4?No. Coinbase International runs FIX 5.0; Coinbase Exchange runs FIX 4.2 for order entry and FIX 5.0 for market data; Coinbase Prime runs FIX 4.2 with a FIX 5.0 API in beta.

Do OKX and Bybit support FIX? Their public developer documentation describes REST and WebSocket APIs and does not include a public FIX API. Firms that require FIX can reach these venues through third-party infrastructure that exposes a FIX interface.

Is there a single FIX standard for crypto? No universally adopted crypto FIX profile exists. The FIX Trading Community runs a Digital Asset Working Group on the topic, but today versions, authentication, and session rules differ from venue to venue.

Sources

Facts verified as of July 2026 against live venue documentation. FIX versions, endpoints, and deprecation dates change; re-check against live docs before reuse.

• Binance Spot FIX API — https://developers.binance.com/legacy-docs/binance-spot-api-docs/fix-api
• Coinbase International FIX API Overview — https://docs.cdp.coinbase.com/international-exchange/fix-api/fix-api-overview
• Coinbase Exchange FIX Connectivity & Order Entry — https://docs.cdp.coinbase.com/exchange
• Coinbase Prime FIX API Connectivity — https://docs.cdp.coinbase.com/prime/fix-api/connectivity
• Kraken FIX Introduction — https://docs.kraken.com/api/docs/guides/spot-fix-intro
• Gemini FIX documentation & Connecting guide — https://developer.gemini.com/trading/fix
• Deribit FIX API Overview — docs.deribit.com/fix-api/production/overview
• Crypto.com FIX API announcement (GEN 3.0) — crypto.com/en/product-news/fixapi
• Bitstamp FIX API launch (2017) and new FIX interface (2022) — blog.bitstamp.net/ ; bitstamp.net/api
• CEX.IO FIX API — cex.io/fix-api
• Bitfinex FIX gateway (bfxfixgw, with Connamara) — github.com/bitfinexcom/bfxfixgw ; blog.bitfinex.com
• OKX API documentation (REST/WebSocket) — okx.com/docs-v5/en
• Bybit API documentation (REST/WebSocket) — bybit-exchange.github.io/docs
• FIX Trading Community — Digital Asset Working Group; "FIX to Support Digital Assets" — fixtrading.org