Interactive Brokers vs IG API
The same fields from the Interactive Brokers record and the IG record, side by side. No winner is picked: which one suits you depends on what you are building.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
What the two records show
Differences you can see in the records themselves. These are counts of what this site holds, not a verdict on either API.
- Interactive Brokers is recorded as a broker with an API of its own. IG is recorded as a broker with an API of its own.
- This site documents 23 endpoints for Interactive Brokers and 49 endpoints for IG. That counts what has been documented here, not what each API offers.
- This site has decoded 511 error codes for Interactive Brokers and 132 error codes for IG.
- The limits register holds 6 limit records for Interactive Brokers and 5 limit records for IG. Each limit record carries its own scope.
- The Interactive Brokers record holds a demo claim, verified at its source. The IG record holds a demo claim, verified at its source. The wording of each is in the Demo row below.
- Claims marked unverified or as sources conflicting: 0 in the Interactive Brokers record and 1 in the IG record. Each is labelled where it appears.
- A quickstart is built here for both.
Interactive Brokers and IG, field by field
| Field | Interactive Brokers | IG |
|---|---|---|
| Kind | Broker with its own API | Broker with its own API |
| API family | TWS API (TCP socket), REST (Client Portal Web API), WebSocket | REST, Streaming |
| How you get access | No key: run TWS or IB Gateway (TWS API) or the Client Portal Gateway and log in via browser (Web API).IBKR TWS API documentation, the IB Gatewaychecked | API keys are only issued to existing live account holders: generate one in My IG > Settings > API keys.How to use IG APIchecked |
| Who can use it | Open, funded IBKR Pro account. The Web API supports only IBKR Pro accounts, and the TWS API lists a funded and opened IBKR Pro account among its requirements.IBKR Web API v1.0 documentation, requirements and limitationschecked | Spread bet and CFD accounts only. Share dealing, ISA and SIPP are not supported (error stockbroking-not-supported).trading-ig FAQ (community source)checked |
| Demo | Partial: paper trading accounts are supported and the Web API is logged in to with a separate paper username; demo accounts cannot subscribe to data.IBKR Web API documentation, using a paper accountchecked | Partial: demo API works, but no key from a standalone demo account unless it is linked to a live account.How to use IG APIchecked |
| Authentication | TWS API: local socket to a TWS or IB Gateway the user has logged in to by hand. Web API: Client Portal Gateway with a browser login on the same machine; the Web API also lists OAuth 1.0a, OAuth 2.0 and SSO, and IBKR's older use cases page gives OAuth as the route for institutional clients.IBKR TWS API documentation, the IB Gatewaychecked | API key plus username and password returns CST and X-SECURITY-TOKEN, valid 12 hours on a rolling basis with each call resetting the clock on the IG Labs FAQ, while IG's REST trading API guide says 6 hours at first, extended up to a maximum of 72 hours: a disagreement between two IG pages that the blocked reference page could not settle on 23 Sep 2026. The v3 OAuth access token lasts as long as the login response says, with a refresh token that expires later. All tokens are invalidated during weekend maintenance.Sources conflict IG Labs FAQ: 12 hours between calls, reset by each call. IG Labs REST trading API guide: 6 hours at first, extended up to 72 hours while in use.IG Labs REST trading API guidechecked |
| Streaming | TWS API is event driven over the socket. The Web API websocket is at /v1/api/ws (wss://localhost:5000/v1/api/ws through the gateway): the number of market data subscriptions depends on the account's market data lines, 100 by default, a market data stream ends after 15 minutes unless it is requested again, and at most 5 historical data requests run at once.IBKR Web API v1.0 documentation, websockets introductionchecked | Streaming runs on Lightstreamer: IG's Streaming API Guide starts by sending you to the Lightstreamer client library, and the server address to connect to comes back from the /session call. By default a connection holds up to 40 simultaneous subscriptions. The guide asks you to contact IG to raise that quota and the FAQ says to manage it by unsubscribing and subscribing as needed; both warn that opening extra connections to get past it may cost you the API key or your API permissions. The streaming API does not take OAuth tokens, only the CST and X-SECURITY-TOKEN pair.IG Labs Streaming API Guidechecked |
| History depth | Bars of 30 seconds or less are not available beyond six months, and expired futures not beyond two years from expiry. IBKR's current TWS API documentation, read on 12 Oct 2026, counts three pacing violations for bars of 30 seconds or less: an identical historical data request within 15 seconds, six or more requests for the same contract, exchange and tick type within two seconds, and more than 60 requests in any ten minute period, with a BID_ASK request counted twice. The Web API endpoint /iserver/marketdata/history has its own published pacing of 10 requests a second or 50 a minute. Executions: since midnight by default, up to 7 days in TWS if its Trade Log setting is changed, and the current day only in IB Gateway.IBKR TWS API documentation, unavailable historical datachecked | Up to 20 years of price history depending on resolution; 10,000 historical data points per week. Transactions and activity history are paged.IG: How to use IG APIchecked |
| Limits |
|
|
| Endpoints documented here | 23 | 49 |
| Error codes decoded here | 511 | 132 |
| Official documentation | interactivebrokers.com | labs.ig.com |
Go deeper on each side
Interactive Brokers
- Interactive Brokers API page, the full record
- Interactive Brokers API quickstart, credentials to a first call
- Interactive Brokers API limits, in the table above
- Interactive Brokers API error codes, each with its fix
- Interactive Brokers API endpoints, each with its source
- Get your Interactive Brokers trade history into a spreadsheet
- IBKR API without TWS: headless IB Gateway options
- The three Interactive Brokers REST front doors compared
- Interactive Brokers MCP servers, compared
IG
- IG API page, the full record
- IG API quickstart, credentials to a first call
- IG API limits, in the table above
- IG API error codes, each with its fix
- IG API endpoints, each with its source
- ChatGPT trading bot with the IG API, the safe way
- Get your IG trade history into a spreadsheet
- IG deal confirms: turning a deal reference into a result
- IG demo API key: how to get one and what it allows
- IG streaming with Python
All comparisons. New to this? Getting started with API trading.