Broker API HubMenu

The three Interactive Brokers REST front doors compared

Interactive Brokers publishes more than one REST front door and they do not point at each other. Here is what each one said on the day we opened it.

Independent and unofficialLast reviewed

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.

Carried over from an earlier version of this site. The links below are the sources it was written from, but its statements have not been re-read at source since the date shown, so check anything you rely on.

The three front doors

Front doorStateWhat we readSource
TWS API referenceCarries an explicit deprecation noticeIt carries an explicit deprecation notice and still serves the full v9.72 reference behind it. A deprecated page that still works is the hardest kind to navigate, because the material is complete and the status is not.interactivebrokers.github.io/tws-api/(deprecated by IBKR, read 23 Sep 2026; IBKR Campus is now the reference)
Campus Web API pageReads as currentIt reads as current and does not mention the Client Portal API v1 page.www.interactivebrokers.com/campus/ibkr-api-page/webapi-doc/
Client Portal API v1 pageReads as currentIt reads as current and does not mention the Campus Web API page. Two pages that both read as current and neither of which names the other leaves the reader to guess which one is canonical.www.interactivebrokers.com/campus/ibkr-api-page/cpapi-v1/

All three opened on 20 Sep 2026. Read earlier and republished here unchanged, with the date of that reading.

Read again in a browser on 12 Oct 2026, the picture had moved. The Client Portal API v1 address on Campus redirected to an address on the documentation site that showed a page not found notice; the v1.0 material now sits at www.interactivebrokers.com/docs/web-api/v1/introduction. The Campus TWS API address redirected to www.interactivebrokers.com/docs/tws-api/doc/introduction. The Campus Web API page still opened, and on that day it did publish rate limits: 10 requests a second through the Client Portal Gateway, with a table of limits for single endpoints. The table above and the section below are the 20 Sep reading, kept as dated.

No rate limits on the Web API page

The Web API page publishes no rate limits. That is a statement about the page we opened on 20 Sep 2026 and not about what the gateway enforces. Limits are published elsewhere by Interactive Brokers, and this site records them on the broker page with the address each one was read from.

The rate limits this site holds for Interactive Brokers, with their sources and dates

Why two third party tools exist

Client Portal authentication is the real pain point, and two of the most starred Interactive Brokers repositories exist to deal with it rather than to wrap the API.

Stars and push dates read 20 Sep 2026 from the api.github.com search endpoint. The full reading is on the GitHub page.

What we are not saying

We have not tested any of these three. We did not call an endpoint, and we are not telling you which one Interactive Brokers intends you to use, because none of the three pages says so. What we are saying is narrower and checkable: on 20 Sep 2026 one carried a deprecation notice and the other two read as current without naming each other.

Where to go next

Sections