Choosing Your Stack · Broker & Execution · Module 2

Broker API Capability Matrix

Ten broker and execution APIs, eight capability axes, every cell dated and cited against official documentation. Where a fact could not be confirmed on an official page this session, the cell says so explicitly rather than guessing. Neutral, unaffiliated -- this is a reference table for choosing infrastructure, not a recommendation.

Choosing your stack — Module 2 hub cluster:

Account & Asset Coverage

Paper trading, options/futures support, and account minimums. Sources: official broker pages, re-verified 2026-07-18 alongside the rest of this matrix.

Broker Paper Trading Options Futures Account Minimum
Interactive Brokers Yes — free, $1M simulated equity, but requires an approved live account first Yes Yes $0 to open; practical futures margin-account minimum is exchange/product-dependent (commonly cited around $2,000 — not independently confirmed on IBKR's own minimums page this session; varies, check broker)
Alpaca Yes — free, real-time IEX/SIP data, no funding required, separate keys and domain Yes No $0
Tradier Yes — sandbox 15-min delayed; production quotes real-time even on an unfunded account Yes No on the documented algo-trading API (see Tradier profile for the separate Tradier Futures entity) $0 (Lite/Pro/Pro Plus tiers; Lite is not commission-free)
TradeStation Yes — SIM mirrors live behavior, same API and auth flow Yes Yes API access free; a funded account (~$10k cited) may apply in practice [approx]
Tastytrade Yes — certification sandbox, resets every 24h, 15-min delayed data Yes Yes Free account
Tradovate Yes — separate demo domain/environment, no time limit No Yes (CME complex; same regulated entity as NinjaTrader Brokerage — see Futures Trading Vendors) No fixed broker-side minimum stated; API access requires a live account with $1,000+ balance to activate
OANDA Yes — fxPractice demo No No $0 (US); spread-based cost
Binance Yes — Spot Testnet No Yes (separate futures product and testnet) Free API; ~0.1% spot fees
Coinbase Advanced Trade No — the "sandbox" is a static mock covering 2 endpoint groups, not a real paper account No No Free API; tiered fees
Robinhood No No official API for options (crypto-only official API) No $0 account

API Mechanics

Streaming, native bracket/OCO support, authentication model, and whether historical bars come through the same API as trading.

Broker Streaming Bracket / OCO Auth Model Historical Data (same API)
Interactive Brokers Yes — WebSocket (Client Portal Web API) and native tick streaming (TWS API) Yes — native bracket orders + OCA groups Session-based Client Portal Gateway login (retail); full OAuth 2.0 for institutional/enterprise access Yes — same entitlement as live streaming, not a separate product
Alpaca Yes — WebSocket (IEX free tier / SIP paid tier) Yes — order_class bracket/oco/oto, one call API key + secret (default); OAuth2 available for third-party apps Yes — same account/keys, separate data.alpaca.markets domain
Tradier Yes — WebSocket Yes — native OTOCO/OCO OAuth2 bearer token (personal non-expiring token, or third-party authorization-code flow) Yes — /markets/history, same domain and auth
TradeStation Yes — HTTP streaming Yes — OCO + OSO/bracket orders (legs must be modified individually after creation) OAuth2 authorization-code flow (PKCE variant available); 20-minute access token Yes — same API and auth as trading
Tastytrade Yes — DXLink WebSocket Yes — OTOCO/OCO/OTO/PAIRS complex-order endpoint, one call OAuth2 bearer, 15-minute access token; separate certification-sandbox login Yes — delivered through the same DXLink streaming connection/token as live quotes
Tradovate Yes — on a separate market-data WebSocket from the trading/account socket Yes — placeoso (bracket) and placeoco endpoints Bearer token (credentials flow or OAuth2); a separate market-data token; fully separate demo/live domains Same socket mechanically, but live/historical data delivery is gated by a separately billed market-data subscription
OANDA Yes — v20 streaming (20 concurrent streams per IP cap) Functional, not a labeled type — take-profit/stop-loss/trailing-stop attached to the entry order Static personal access token; separate tokens required for practice vs live Yes — /instruments/candles, same token
Binance Yes — public WebSocket (no auth) plus a private, authenticated user-data stream Yes — native OCO; newer OTO/OTOCO order-list types also available (exact rollout date not independently reconfirmed this session) API key + secret (HMAC legacy, RSA, or Ed25519) Yes — /klines, same domain and auth
Coinbase Advanced Trade Yes — WebSocket (public channels plus JWT-gated private channels) Yes — trigger_bracket configuration; no separately named OCO type CDP JWT (ES256 or EdDSA signing), 2-minute token expiry Yes — /candles, same JWT auth
Robinhood No streaming confirmed — poll-based best-bid/ask only on the official crypto API; varies, check broker No bracket/OCO order type found in the official crypto API API key + request signing; crypto-only, no sandbox environment Varies — check broker (no historical-bars endpoint confirmed this session)

How to Read This Matrix

What this page does not cover: execution quality, fill latency, spreads, or any performance/P&L outcome for any venue — those require your own due diligence with real capital. For the full 11-venue broker overview, see Broker APIs; for a deep single-broker profile, see Tradier; for futures-specific infrastructure beyond these broker APIs, see Futures Trading Vendors. AlgoDrill has no commercial relationship with any venue listed here.


Frequently Asked Questions

Which broker APIs support native bracket or OCO orders?
Eight of the ten venues in this matrix support server-side bracket and/or OCO orders in a single API call: Interactive Brokers (bracket + OCA groups), Alpaca (order_class bracket/oco/oto), Tradier (native OTOCO/OCO), TradeStation (OCO/OSO, though legs must be modified individually after creation), Tastytrade (OTOCO/OCO/OTO/PAIRS complex orders), Tradovate (placeoso/placeoco endpoints), Binance (native OCO, with newer OTO/OTOCO order-list types), and Coinbase Advanced Trade (trigger_bracket configuration, no separately named OCO type). OANDA achieves the same result functionally via take-profit/stop-loss/trailing-stop orders attached to an entry order rather than a labeled bracket type. Robinhood's crypto-only API has no bracket or OCO order type at all.
Which broker APIs offer a real, funded-free paper trading account?
Alpaca, Tradier, TradeStation (SIM), Tastytrade (certification sandbox), Tradovate (demo environment), OANDA (fxPractice), and Binance (Spot Testnet) all offer a genuine simulated trading environment with no funding required. Interactive Brokers' paper account is free and well-resourced ($1,000,000 simulated equity) but requires an approved live account first -- not an instant no-signup demo. Coinbase Advanced Trade's 'sandbox' is a static, unauthenticated mock environment covering only two endpoint groups, not a functioning paper-trading account. Robinhood has no paper trading mode at all.
Which brokers in this matrix support futures trading via their API?
Interactive Brokers, TradeStation, Tastytrade, Tradovate, and Binance (via a separate futures product and testnet) support futures. Alpaca, Tradier (on its documented algo-trading API -- see the Tradier profile), OANDA, Coinbase Advanced Trade, and Robinhood do not. For futures-specific infrastructure vendors beyond these broker APIs, see the futures-vendor coverage page.
What authentication model do most broker APIs use?
It splits roughly three ways. Static API key + secret is used by Alpaca (default), Binance, and Robinhood. Bearer tokens issued via an OAuth2 flow are used by Tradier, TradeStation, Tastytrade, Tradovate (credentials or OAuth2), and Coinbase Advanced Trade (short-lived JWTs). Interactive Brokers and OANDA are the outliers: IBKR's retail path is a session-based Gateway login rather than a token at all, while OANDA uses a static personal access token but requires a separate token for its practice environment. Paper/sandbox credentials are usually distinct from live credentials across all of them.
Is Coinbase Advanced Trade's sandbox a real paper trading account?
No. Coinbase's sandbox environment returns static, pre-defined canned responses for a limited set of endpoints (accounts and orders only) rather than simulating live order fills against real market prices. That makes it useful for testing whether your client code parses responses correctly, but not for evaluating strategy behavior the way Alpaca's, Tradier's, or OANDA's genuine paper/practice environments do.

Drill broker API capabilities, auth models, and bracket-order architecture with AlgoDrill's spaced-repetition flashcards.

Start Flashcards →   View Reading List →