ibeam VS interactive-broker-python-api

Consider IBeam for authenticating with the IBKR API and maintaining it authenticated. It's Docker image, you just run it parallel to your trading app.

ps. I also have a couple of other open source libraries: for scheduled data flow (Databay) and for algo trading (IBeam).

One thing that isn't entirely clear is that you have to install a Java-based "gateway" on your local network and proxy all API access through that. Their website claims that it's headless, but it really isn't. I asked CS about that once and it seems that "headless" does not mean what we think it means. There are multiple projects that try to bridge the definitions, with varying degrees of success. I use Voyz/ibeam FWIW.

For logging in and keeping the session alive you might want to look into using ibeam. I wrote my own version before coming across ibeam and have been using that successfully. I should note that I have a private fork with a bunch of additional fixes so let me know if you're interested in trying it out and I'll push those.

Not personally tried, but Im running on ARM and while i was looking at using IB i was looking at using https://github.com/Voyz/ibeam as a docker container.

I recently built a library called IBeam that handles the CP Gateway authentication - consider giving it a shot 😊

Bit late to the party, but I thought I'd mention IBeam - it handles the authentication and maintaining the CP Web Gateway running. The `areed1192/interactive-broker-python-api` you linked u/TankorSmash has useful Python handlers for various API endpoints, but in my experience it doesn't handle the CP Web Gateway authentication and maintenance well.

Hey it's Voyz here - thanks u/dlevac for sharing IBeam :)

Thank you Good-Educator 😊 Unfortunately you still need to perform that, although there is some discussion into automating that too using an automated SMS postbox and a server that stores the passcode. Have a look at this issue: https://github.com/Voyz/ibeam/issues/8

It's pretty clear that the Client Portal API in concert with this library, looks easy to work with from a developer's standpoint. But based on comments here from the past few months it appears that it can be flaky. So much so that a user here created a library to try to maintain the connection. But yesterday I managed to successfully stream market data for a single contract for about an hour with no issues.