Brokers And Platforms
Broker, platform, signal, and protocol connectors
Connect broker-market accounts, trading platforms, webhook signals, and institutional-style protocols only after the customer account supports the workflow.
Setup posture
Save only the keys needed for the selected workflow. A stored credential does not grant live trade authority by itself; mode, license, adapter, account permission, and deterministic risk checks still apply.
Connector Details
15 connector slots in this lane
The details below explain what each provider is for, where customers create the key, and what permission posture should be used first.
Broker adapter
6 supported slots
AlpacaVault-ready
Paper/live broker API slot for supported stocks, ETFs, snapshots, orders, and positions.
Key setup: Create Alpaca paper credentials first, then add live credentials only when ready.
Safe permissions: Keep paper and live keys separate and avoid permissions outside the selected workflow.
Open Alpaca docsInteractive BrokersAdapter-ready
Broker-market adapter slot for account, position, and order workflows where enabled.
Key setup: Use the broker API access path supported by the account and region.
Safe permissions: Start with account and paper-style permissions before live order authority.
Open IBKR API docsSaxo OpenAPIAdapter-ready
OpenAPI broker connector slot for account, positions, prices, and order workflows where eligible.
Key setup: Use Saxo developer access and OAuth/app credentials for the eligible account.
Safe permissions: Begin with account and market-data access before enabling order workflows.
Open Saxo OpenAPI docsSchwab Trader APIAdapter-ready
Broker API slot for account, quote, and order workflows where the customer account supports it.
Key setup: Create a Schwab developer app and connect only the intended brokerage account.
Safe permissions: Keep live trading disabled until entitlement, paper review, and risk rules are validated.
Open Schwab developer portalTradierAdapter-ready
Broker API slot for equities/options workflows where enabled by the customer.
Key setup: Create a Tradier API token for the approved account environment.
Safe permissions: Use only the permissions required for the configured broker workflow.
Open Tradier docsIG MarketsAdapter-ready
UK broker-market connector slot for account and market workflows where approved.
Key setup: Create an IG API key from the account's API/developer settings.
Safe permissions: Check account eligibility and keep live dealing disabled until paper review is complete.
Open IG docsBroker / FX
1 supported slot
OANDAAdapter-ready
FX and CFD-style broker API slot where customer account permissions and region allow it.
Key setup: Create an OANDA REST API token in the customer account.
Safe permissions: Use practice credentials first and check regional eligibility before live use.
Open OANDA docsBroker / CFD
1 supported slot
Capital.comAdapter-ready
CFD-style market and account API slot where the customer account and region permit API use.
Key setup: Create API credentials inside the Capital.com account if API access is available for the region.
Safe permissions: Use demo credentials first and verify regional product restrictions before live use.
Open Capital.com API docsTrading platform bridge
4 supported slots
MetaTrader 5Adapter-ready
MT5 bridge slot for broker accounts that expose market data and order workflows through MT5.
Key setup: Connect through the customer's own MT5 terminal/account bridge where supported by the broker.
Safe permissions: Keep broker passwords out of ZeroTrade vaults; use dedicated bridge credentials where possible.
Open MT5 Python docscTrader Open APIAdapter-ready
Open API bridge slot for customer-authorised cTrader accounts and trading-oriented apps.
Key setup: Register an Open API app and authorise only the intended cTrader account.
Safe permissions: Use explicit account authorisation and revoke the app if the workflow is no longer used.
Open cTrader Open API docsTradeLockerAdapter-ready
Trading-platform API slot for supported accounts, quotes, and order workflows.
Key setup: Create TradeLocker API credentials where the customer's account supports API access.
Safe permissions: Start read-only or demo where available and separate it from unrelated account credentials.
Open TradeLocker docsNinjaTraderAdapter-ready
NinjaTrader developer/API bridge slot for supported futures and platform workflows.
Key setup: Use NinjaTrader developer/API credentials only for supported platform workflows.
Safe permissions: Keep local platform bridges isolated and test with simulation before any live action.
Open NinjaTrader API docsFutures adapter
1 supported slot
TradovateAdapter-ready
Futures account and market connector slot for approved automated workflows.
Key setup: Request/enable Tradovate API access and complete any required attestation.
Safe permissions: Use demo/simulation first and respect futures risk, margin, and data entitlements.
Open Tradovate API access notesSignal ingress
1 supported slot
TradingView WebhooksVault-ready
Webhook alert ingress slot for customer-owned chart alerts before validation and risk gates.
Key setup: Create a signed ZeroTrade webhook endpoint and paste it into the customer's TradingView alert.
Safe permissions: Treat TradingView as signal ingress only; alerts still need validation and risk approval.
Open TradingView webhook docsInstitutional protocol
1 supported slot
FIX GatewayAdapter-ready
FIX-style venue protocol slot for higher-grade broker or exchange integrations.
Key setup: Use venue-issued FIX session credentials only after the broker/venue approves the integration.
Safe permissions: FIX sessions require strict network, certificate, sequence, and kill-switch controls.
Open FIX standards