Why choose Client Portal Web API over TWS/IB Gateway for this project?

[one-littlebear]

Hi Ruben—thanks for open sourcing this project!

I’m curious about your design choice to build on the Client Portal Gateway (Web API) rather than the TWS/IB Gateway socket API.

I noticed the Web API’s trade-offs in the repo (session keepalive via tickler, browser-based login on the same machine, unsupported /gw/api/OAuth endpoints, and current manual routers due to OpenAPI specs.).

Given those, did you consider using the TWS API instead?

Best regards

[rcontesti]

Hi @one-littlebear, great question! This is a bet. A bet that the WEB API will be a reliable comprehensive option. I have added a short motivation section in README.MD file. For the time being it serves my purposes. But agree that for most people focused on trading, TWS is a better option. Best, Ruben.

[one-littlebear]

Hi Ruben, thanks for the thorough explanation! I take it that you are then more interested in "administrative" tasks like maybe reporting or account tracking rather than active trading? (Hope, you don't mind me asking.)

Best regards,
Hoc

[rcontesti]

I'm interested in both because I need them both. I need to keep a proper P&L. In the case of an MCP, where there is thinking involved and thus latency, I believe is better to use the WEB API. For trading, I would never use an MCP. At least for the time being. I could be wrong. Just my take on the topic.