Interactive Brokers FAQ: 160+ Questions Answered

1. Manual only -- no automated alert execution
2. Order execution delays (25-45 seconds reported by users)
3. Limited order types (no OCA, no complex brackets)
4. Single account only
5. Symbol mapping issues between TV and IB tickers
6. Cannot execute during extended hours from TV
7. No Pine Script strategy-to-order pipeline

Yes. Webhooks require at minimum a TradingView Pro plan ($14.95/month billed annually). The free plan doesn't support webhook URLs in alerts. Higher tiers (Pro+, Premium) allow more active alerts and potentially faster alert processing.

Total end-to-end: 2-10 seconds normally, up to 60 seconds during high load. Breakdown:
TradingView alert processing: 1-5 seconds
Webhook HTTP delivery: 0.1-0.5 seconds
Middleware processing: 0.1-1 second
IB order submission: 0.1-0.5 seconds
Exchange acknowledgment: 10-50ms

This makes webhook-based automation suitable for swing trading and position strategies, but not for scalping or HFT.

Alerts send JSON in the webhook body. A typical PickMyTrade format:

{
  "action": "buy",
  "symbol": "AAPL",
  "qty": 100,
  "order_type": "limit",
  "price": {{close}},
  "stop_loss": {{close * 0.98}},
  "take_profit": {{close * 1.05}}
}

TradingView supports dynamic placeholders: {{close}}, {{ticker}}, {{volume}}, {{time}}. Each middleware has its own JSON schema -- check their docs for exact syntax.

With a custom solution this requires complex multi-account management. PickMyTrade makes this simple: connect up to 20+ accounts, and each alert automatically executes across all connected accounts with proper position sizing. This is one of the most requested features that's extremely difficult to build yourself.

Yes, via PickMyTrade. Specify the futures contract in your alert (e.g., ES, NQ, MES, MNQ, CL) and the platform handles contract resolution, rollover awareness, and order routing to IB. PickMyTrade is particularly popular for futures automation because it handles the complexity that TradingView's native IB integration doesn't support.

Architecture: TradingView webhook → Python web server (Flask/FastAPI) → IB API library (ib_async) → IB Gateway. You'll need: a TradingView Pro+ subscription (webhooks), a publicly accessible server (cloud VPS), IB Gateway with IBC for auto-login, and robust reconnection/error handling code. This is a significant engineering project -- expect weeks of development and ongoing maintenance. For most traders, a managed service like PickMyTrade is more cost-effective.

Common causes: 1. Alert conditions not met (check your Pine Script logic). 2. Alert expired or hit the trigger limit. 3. TradingView server load during high-volatility events delays alert processing. 4. Webhook URL is incorrect or the receiving server is down. 5. TradingView plan limit on active alerts reached. 6. Pine Script error causing the alert to fail silently. Check TradingView's Alert Log for delivery status.

Yes, but IB's crypto offering is limited (BTC, ETH, LTC, BCH via Paxos). Only Market (with IOC) and Limit orders are supported -- no bracket orders for crypto. For broader crypto automation, PickMyTrade supports dedicated crypto brokers like Binance and Bybit alongside IB, all from the same TradingView alerts.

Every IBKR Pro account automatically includes a paper trading account. In TWS: File → Login → select "Paper Trading". In IB Gateway: choose "Paper Trading" mode on startup. Paper accounts start with $1,000,000 in virtual funds. API ports: 7497 (TWS paper) or 4002 (Gateway paper). Account IDs start with "DU" (vs "U" for live).

Yes -- paper trading uses the same market data feeds as live trading. If you have paid subscriptions, you get real-time data in paper mode. Without subscriptions, you'll see delayed data. Forex and crypto are always real-time.

IB's paper simulator has known limitations: market orders may show PendingSubmit for seconds, limit orders may not fill even at the right price, stops may not trigger with delayed data. Paper trading is useful for testing code flow and connectivity, not realistic fill simulation. For realistic backtesting, use a proper backtesting framework (QuantConnect, Backtrader, etc.).

IBKR Lite does not support API access (live or paper). You need IBKR Pro for API-based paper trading. However, you can use TWS paper trading with IBKR Lite for manual testing via the GUI.

Client Portal → Settings → Paper Trading Account → Reset. This clears all positions and resets to $1,000,000. The reset may take a few hours. You cannot set a custom starting balance.

Yes. IB may close paper accounts that are inactive for extended periods. Treat paper accounts as disposable testing environments -- don't store important strategy state only in the paper account. Keep all critical data in your own database.

Paper uses simplified matching (no real market microstructure), may fill slower than real markets, and doesn't experience slippage or partial fills. Live trading has real liquidity, genuine order book interaction, and actual market impact. Code that works in paper may behave differently live.

Yes. Paper trading supports all asset classes available in your live account: stocks, options, futures, forex, crypto. You need the appropriate trading permissions enabled on your account (even for paper). Margin calculations in paper trading follow the same rules as live.

Absolutely yes. Always test on paper first to verify: connection handling, order placement logic, position tracking, reconnection behavior, and error handling. Run paper for at least a few days including overnight sessions and the nightly restart. Just remember that paper fills are not realistic -- don't use paper trading P&L as a predictor of live performance.

Use environment variables or config files. Change the port number (7497 paper vs 7496 live for TWS, 4002 vs 4001 for Gateway). Always add a safety check: verify the account ID starts with "DU" (paper) or "U" (live) to prevent accidental live trading during testing.

Yes, through a Financial Advisor (FA) or Friends & Family account structure. One master login controls multiple sub-accounts. You can view positions, place trades, and allocate orders across all accounts from a single TWS session. For non-FA accounts, each account needs its own separate TWS/Gateway session with a unique username.

An FA account lets you manage client accounts under a single login. You can create account groups, allocation profiles, and model portfolios. Orders can be allocated by EqualQuantity, NetLiq (proportional to net liquidation), or AvailableEquity. Minimum requirements vary by region -- contact IB for FA account setup.

Account Management → Settings → Users & Access Rights → Add User. Create a user with API trading permissions. This lets your bot run on a dedicated login while keeping your primary login for the web interface, avoiding "competing session" conflicts.

Yes. Use different clientId values (1-32) for each strategy script. Each clientId creates an independent API connection that only sees its own orders. Up to 32 strategies can run simultaneously on one account. Keep in mind that positions are shared at the account level -- coordinate between strategies to avoid conflicts.

The second connection kicks out the first. IB only allows one active connection per clientId. Use unique clientIds for each script.

clientId=0 is the "master" client. It can see and access ALL orders, including those placed manually in TWS. Non-zero clientIds only see orders they placed. Use clientId=0 for monitoring/dashboard applications. Never use clientId=0 for automated strategies to avoid accidentally interfering with manual trades.

PickMyTrade routes a single TradingView alert to 20+ connected accounts simultaneously. Each account can have custom position sizing, different instruments, and independent SL/TP settings. No FA account structure needed -- PickMyTrade works with standard individual accounts across multiple brokers (IB, Tradovate, Rithmic, and more).

The master client can view all open orders but cannot modify or cancel orders placed by other clientIds. Only reqGlobalCancel() can cancel all orders regardless of clientId.

Three allocation methods: EqualQuantity (split evenly), NetLiq (proportional to each account's net liquidation value), AvailableEquity (proportional to available equity). Set via order.faGroup and order.faMethod in the API, or through the allocation dropdown in TWS.

IB doesn't natively tag positions by strategy. Best practices: 1. Use different clientIds per strategy and track orders by clientId. 2. Use IB's Model Portfolios (FA accounts) to group positions logically. 3. Maintain your own database mapping each trade to a strategy. 4. Use order reference strings (order.orderRef) to tag trades with strategy identifiers.

The IBKR Mobile app (iOS/Android) supports: real-time quotes and charts, all major order types, portfolio monitoring, account management, 2FA authentication, scanner, and alerts. It's surprisingly full-featured for a mobile app. However, it doesn't support API connections or webhook automation.

Client Portal is IB's web-based platform at portal.interactivebrokers.com. It handles: account management, fund transfers, market data subscriptions, statements/reports, tax documents, trading permissions, user management, and basic trading. It's the primary interface for non-trading account tasks.

Be careful. Logging into IBKR Mobile or Client Portal may create a competing session that disconnects your API bot. Create a secondary username for your bot to avoid this. With separate usernames, you can trade manually from your phone while your bot runs independently.

Yes. The IBKR Mobile app supports Face ID (iPhone), Touch ID (iPhone/iPad), and fingerprint authentication (Android) for 2FA. This is the fastest way to handle the weekly re-authentication requirement for API sessions.

IB accepts clients from 200+ countries. However, you cannot access your account from OFAC-sanctioned countries (Cuba, Iran, North Korea, Syria, etc.). IB monitors login locations and may require additional verification for unusual access patterns. Using a VPN to trade is against IB's terms of service if it masks your true location.

GlobalTrader is IB's simplified mobile app for casual investors. It offers a streamlined interface for buying/selling stocks, ETFs, and fractional shares. It does NOT support futures, options, API access, or advanced order types. If you need automation or advanced features, use the main IBKR Mobile app or TWS.

In TWS: right-click a symbol → Create Alert. Set conditions based on price, volume, margin, percentage change, or time. Alerts can trigger: popup, sound, email, SMS, or order submission. On IBKR Mobile: tap the bell icon on any quote. Alerts persist across sessions and work even when TWS is closed (server-side).

Client Portal supports basic trading (stocks, options, forex), but it's significantly less capable than TWS. For active trading, TWS or IBKR Mobile are better choices. Client Portal is best for account management, reporting, and occasional trades.

Yes. IB offers a TWS demo at interactivebrokers.com/en/trading/tws-demo.php. No registration required. The demo uses simulated data and lets you explore TWS features, but it doesn't connect to real markets or support API access. For API testing, you need a real account with the paper trading mode enabled.

Client Portal → Help → Message Center (ticket system, usually 1-2 business days). Phone support: available 24/6 at country-specific numbers listed on the IB website. Live chat: available in Client Portal during business hours. IB's support is known for being technically knowledgeable but sometimes slow to respond. For API-specific questions, the IB API forum and community resources are often faster.

IB auto-liquidates when your account falls below maintenance margin. Unlike other brokers, IB does not issue margin calls -- it liquidates directly and automatically. This can happen during volatile moves even when you're away. Prevention: maintain adequate margin cushion (watch the "Cushion" metric), use smaller position sizes, and set up margin warning alerts in TWS/mobile.

Common rejection reasons: 1. Insufficient margin/buying power. 2. Missing trading permissions (enable in Account Management → Trading Permissions). 3. Market order outside trading hours (use limit orders). 4. PDT restriction (need $25K for day trading). 5. Penny stock restrictions. 6. Short selling restrictions (stock not borrowable). 7. Price cap limits on options orders. Check the TWS error message for the specific reason.

1. Increase Java memory: File → Global Configuration → General → increase memory allocation to 4096MB. 2. Close unused watchlists, charts, and windows. 3. Reduce the number of active market data subscriptions. 4. Restart TWS periodically (especially after running for days). 5. Use the Stable version instead of Latest. 6. Close browser tabs -- Java and browser compete for RAM.

IB's API reflects 25+ years of features across every asset class and 150+ exchanges. The complexity comes from: asynchronous callback architecture, event-based error handling (no exceptions), strict rate limiting, mandatory TWS/Gateway dependency, and IB-specific conventions. This is a common frustration -- "IB is a great brokerage with terrible APIs" is one of the most upvoted sentiments on r/algotrading. The trade-off is unmatched market access and features.