- ago
Interactive Brokers seems quite popular for algo traders. However, doing anything with IBKR requires using a local API gateway for access. Most of these connections tend to run off of TWS/IBGateway (like WL8). In my own experience (and that of other traders I know), IBKR's connections using this method aren't rock solid (I'm being nice). On top of that, both the TWS and IBGateway programs require the Java Runtime Environment and are terrible on system resources.
Has anyone experimented with using the client portal application instead?
What are the chances that the current IBKR extension gets this capability or is this already possible?
Idk why IBKR is so far behind on adding direct API access (they have it, but only for commercial clients it looks like), but using their software to act as a gateway just adds extra opportunities for Murphy to check out what's going on and get involved.
I see that it is possible to build our own BrokerAdapter, but it seems like it would be much easier to add this option into the already existing adapter than it would be to build an entirely new one from scratch.
It looks like the IBKR client portal is pretty small in comparison to the other options. It might require a little more know-how on the users end to setup (looks like docker is the best option). It also looks like it requires far less system resources to run that the other options.
I'm just thinking out loud (via the keyboard), so feel free to correct me if I am wrong about my assumptions.
Has anyone experimented with using the client portal application instead?
What are the chances that the current IBKR extension gets this capability or is this already possible?
Idk why IBKR is so far behind on adding direct API access (they have it, but only for commercial clients it looks like), but using their software to act as a gateway just adds extra opportunities for Murphy to check out what's going on and get involved.
I see that it is possible to build our own BrokerAdapter, but it seems like it would be much easier to add this option into the already existing adapter than it would be to build an entirely new one from scratch.
It looks like the IBKR client portal is pretty small in comparison to the other options. It might require a little more know-how on the users end to setup (looks like docker is the best option). It also looks like it requires far less system resources to run that the other options.
I'm just thinking out loud (via the keyboard), so feel free to correct me if I am wrong about my assumptions.
Rename
Check this out: Implement IB Client Portal (REST) API to bypass TWS
- ago
#2
QUOTE:Actually, it's a completely different implementation, so no matter who does it - it will be from scratch.
it seems like it would be much easier to add this option into the already existing adapter than it would be to build an entirely new one from scratch.
The Web API still lacks documentation and several features offered by the TWS API. It's worth looking into eventually, but it's a relatively large programming and testing job.
- ago
#3
I wasn't thinking about the Web API for IBKR. Not only is it not documented well, but it also actually isn't available for regular accounts, despite the fact that it says it is in the docs. Right now, it appears that it is only available for commercial clients.
I was speaking just about the Client API tool. What I don't think I realized was that it is a REST API and that TWS/IBGateway isn't RESTful, then you are right. It would be a complete rewrite.
Looks like TradeStation is gonna be the go to for now. haha
I was speaking just about the Client API tool. What I don't think I realized was that it is a REST API and that TWS/IBGateway isn't RESTful, then you are right. It would be a complete rewrite.
Looks like TradeStation is gonna be the go to for now. haha
- ago
#4
Actually, this is the first I've heard about the Client Portal API. This looks interesting!
I don't read this as available only to institutional clients -
In order to use Client Portal API, a lightweight API gateway, or in the case of institutional clients, OAuth or a dedicated connection, is required,...
We already use OAuth for several of our broker connections, so that's not even a problem. We'll study it!
I don't read this as available only to institutional clients -
In order to use Client Portal API, a lightweight API gateway, or in the case of institutional clients, OAuth or a dedicated connection, is required,...
We already use OAuth for several of our broker connections, so that's not even a problem. We'll study it!
Your Response
Post
Edit Post
Login is required