DATASET · BROKER API CAPABILITIES
Broker API Matrix for Algorithmic Trading
A structured broker API matrix covering asset classes, REST, WebSocket, FIX, paper trading, testnet, market data, order APIs, SDKs, official documentation, and verification status.
How to use this matrix. Treat each row as an integration starting point, not a guarantee of account access. Capabilities vary by region, product, account, permission, environment, and entitlement. Follow the official documentation link and verify the exact capability before production execution.
| Broker | Asset classes / scope | REST / streaming note | Paper / testnet | FIX | Rust SDK | Official documentation | Last verified |
|---|---|---|---|---|---|---|---|
| Binance | Crypto spot, margin, and derivatives APIs vary by product and jurisdiction. | REST and WebSocket APIs are documented; confirm product-specific endpoints and permissions. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| OKX | Crypto spot, margin, derivatives, and account APIs vary by instrument type. | REST and WebSocket APIs are documented; instrument type and account mode are material. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Bybit | Crypto spot, derivatives, and account APIs vary by category. | REST and WebSocket APIs are documented; category must remain part of routing. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Interactive Brokers | Multi-asset brokerage APIs with account, market data, and order workflows. | Client Portal, TWS, and FIX options have different deployment and session models. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Futu | Hong Kong, US, and other supported market products depend on account and region. | OpenD and protocol APIs require explicit session and entitlement handling. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Tiger Brokers | Broker API availability depends on entity, region, and account permissions. | Confirm SDK, market data, and order capabilities with the relevant official documentation. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Longbridge | Multi-market brokerage API coverage depends on account and product. | REST and streaming interfaces require account and market entitlements. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Alpaca | US equities, options, and crypto availability depends on account and product. | REST and streaming APIs are documented; paper and live environments must remain explicit. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| TradeStation | US brokerage API coverage depends on account and market data permissions. | REST and streaming APIs are documented; token lifecycle and environment matter. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| IG | CFD and spread-betting products vary by region and account. | REST and streaming interfaces have account, session, and rate-limit constraints. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
| Charles Schwab | US brokerage API coverage depends on approval, account, and product access. | Confirm market data and order permissions from the official developer portal. | Confirm | Unknown | Unknown | Official docs | 2026-09-28 |
Data model
The page is generated from the broker data in scripts/generate-knowledge-base.mjs. Broker pages, this table, JSON-LD, RSS links, and sitemaps are generated from the same route set so a capability is not maintained in multiple hand-edited tables.
Sources
Last verified: 2026-09-28. Provider capabilities can change by region, account, product, environment, and entitlement; verify the linked official documentation before production use.