-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration to IBKR broker #184
Comments
Hey @machinevisionbeans we've definitely looked into this before. We don't use IBKR ourselves so we've had a hard time planning the integration. We are happy to accept integration contributions though :). |
Just curious, we might be able to integrate IBKR into the base package with the external API. We might also make it easier by hosting the IBKR API for you via the Blankly Platform. So we're thinking about it....love to hear your thoughts |
That would be fantastic to offer IBKR as an exchange on blankly app. It would make it possible to leverage on the bot hosting services. IBKR is a big brokerage in here southeast asia, Australia and new zealand |
Would also love to see this. Thank you. //EDIT: If you do decide to offer a hosted API - which I absolutely understand because the TWS API is a PITA - please make sure not to limit usage to your hosted API. We cannot use this institutionally, and it needs to be noted that IBKR is a frequently seen brokerage for hedge funds in the US as well. |
Awesome! Yeah we’ll take a look at this! @aggregated love to hear more about how we could work with you guys institutionally! Are you part of our discord by chance? |
I'm not, sorry, I'm confined to certain compliant communication channels, but we are looking into you these days and I will send an email to the email address listed in your profile. |
any update on this? IBKR is one of the few brokers that offer both UCITS ETFs (for EU traders) and an API |
Not yet we have discussed it but don't have the dev resources to make it happen yet. |
Request for API integration for IBKR brokerage.
The text was updated successfully, but these errors were encountered: