CEX API / SDK ecosystem comparison — developer interfaces of domestic / overseas exchanges

Wiki route

This entry sits under exchanges index. Read it against Global CEX ranking reference guide for peer / contrast context and FSA crypto-asset exchange registration system — number system / Local Finance Bureau jurisdiction / registration requirements for the broader system / regulatory boundary.

Overview

The developer interfaces exposed by CEXs are broadly standardized across 3 tiers: (a) REST API (order placement · balance lookup · trade history · KYC settings, etc. — state-changing + snapshot category), (b) WebSocket (real-time order-book data · price streams · own-fill push — low-latency push category), (c) FIX 4.4 / 5.0 (for institutional prime brokers · offered only by some major CEXs). Primary uses are bot trading, institutional connectivity, data acquisition (material for on-chain analytics / market making), and own-wallet connectivity (exchange ⇔ self-custody round trips). Rate limiting + IP allowlist + API-key signature authentication (HMAC-SHA256) are common across the board.

Major domestic CEX APIs

• bitFlyer: REST + WebSocket (Lightning API) · public · API key + signature authentication · rate limit 30 req/sec · the most veteran domestically, with a large developer community
• GMO Coin, Inc. — Japan crypto-asset exchange operator overview: REST + WebSocket · supports all listed pairs on spot + derivatives · high level of developer-documentation completeness
• bitbank: REST + WebSocket · spot-centric · well-regarded order-book data quality
• Coincheck: REST · simple spec · weaker on the institutional side (retail-leaning)
• Jp Exchange SBI Vc Trade: REST · partial SDK · bank-affiliated, oriented toward institutional connectivity

Major overseas CEX APIs

• Binance: REST + WebSocket + FIX (institutional) · widest global coverage · full product support across spot / futures / options · official Python / Node / Java SDKs
• Coinbase Advanced (formerly Pro): REST + WebSocket + FIX · axis on US institutional connectivity · high regulatory affinity
• OKX: REST + WebSocket + FIX · multi-product (spot / perp / options / structured)
• Bybit: REST + WebSocket · derivatives-centric · perp liquidity world-top
• Kraken Pro: REST + WebSocket + FIX · long-established · oriented toward institutional connectivity

Third-party libraries + aggregators

• CCXT: open source · Python / JS / PHP library integrating 100+ CEXs · de facto standard
• Hummingbot: market-making bot framework · CEX + DEX cross
• Hyperliquid Python SDK: perp-DEX family · a porting target for institutional algos
• TabTrader / 3Commas: retail bot platform · bundles multiple exchanges via API keys

Institutional connectivity standards

• FIX 4.4 / 5.0: bank / brokers standard · offered only by some of Binance / Coinbase / OKX / Kraken
• Via prime broker: indirect connectivity via B2C2 / FalconX / Cumberland (FIX-standardized)
• WebSocket multiplexing: low-latency connections for high-frequency · co-location services are still immature
• API rate limits: differ between spot vs derivatives · institutions use IP multiplexing + sub-account strategies
• Domestic CEXs offer almost no FIX → institutional connectivity depends on major overseas platforms + prime brokers

Related

• global-cex-top10-comparison · global-perp-dex-five-comparison
• jp-crypto-market-maker-otc-layer

Source: compilation of public information (each CEX’s official API documentation, GitHub public SDK repositories, OSS integration libraries such as CCXT/Hummingbot)