-
Updated
Jun 8, 2020 - C#
#
interactive-brokers
Here are 68 public repositories matching this topic...
Algorithmic trading and quantitative trading open source platform to develop trading robots (stock markets, forex, crypto, bitcoins and options).
c-sharp
finance
crypto
trading
forex
cryptocurrency
markets
broker
trading-platform
trading-strategies
quantitative-finance
fixprotocol
hft-trading
algorithmic-trading-engine
nasdaq
stocksharp
trading-robots
bitcoins
interactive-brokers
iqfeed
ezIBpy, a Pythonic Client for Interactive Brokers API
-
Updated
Dec 29, 2019 - Python
Java/MySQL live algorithmic trading using Interactive Brokers API
finance
trading
algo-trading
low-latency
trading-strategies
hft
ctp
quantitative-trading
tws
interactive-brokers
xtp
ib-gateway
price-feed
-
Updated
Oct 25, 2018 - Java
Helps you with managing your investments
finance
investments
portfolio-optimization
stocks
asset-allocation
interactive-brokers
portfolio-rebalancing
tax-statement
-
Updated
Jun 8, 2020 - Rust
Interactive Brokers Trading Gateway running in Docker
-
Updated
May 3, 2020 - Shell
Vectorized backtester and trading engine for QuantRocket
-
Updated
May 25, 2020 - Python
IbPy-like interface for the Interactive Brokers Python API
-
Updated
Mar 9, 2020 - Python
Historical market data downloader using Interactive Brokers TWS
-
Updated
May 17, 2019 - Python
Interactive Brokers TWS API -- Historical data downloader
-
Updated
Apr 10, 2018 - Python
Container to host Interactive Brokers trading system logic written in Javascript.
-
Updated
May 22, 2018 - JavaScript
Analysis of Interactive Brokers reports for tax reporting in Russia
-
Updated
May 24, 2020 - Python
A high-frequency trading model using Interactive Brokers API with pairs and mean-reversion in Python
python3
hft
algorithmic-trading
backtesting-trading-strategies
pairs-trading
interactive-brokers
statistical-arbitrage
livedata
ibapi
backtester-python
-
Updated
Oct 8, 2019 - Python
Interactive Brokers API - GoLang Implement
-
Updated
Jun 9, 2020 - Go
Monkey patches to grease the Interactive Brokers Python API
-
Updated
Aug 20, 2018 - Python
sphqxe
commented
Apr 26, 2020
I notice that you have actually left comments documenting each function, but they are not in standard format (see here) and hence they don't show up in the automatically generated documentation when I ran cargo doc.
Is this intended? If not I wouldn't mind helping to reformat the comments so that the documentation can be automa
A Julia implementation of Interactive Brokers API
-
Updated
May 17, 2020 - Julia
An asynchronous implementation of an Interactive Brokers API client.
-
Updated
May 14, 2018 - Python
Market Data collector for Interactive Brokers
-
Updated
Jun 6, 2018 - C#
Command line interface and Python client for QuantRocket
-
Updated
Jun 8, 2020 - Python
Interactive Brokers - TWS API v9.72+ (Client)
-
Updated
Sep 19, 2018 - C#
Interactive Brokers Gateway as a Docker image
-
Updated
May 16, 2020 - Dockerfile
Interactive Brokers reactive C# API.
-
Updated
Oct 11, 2019 - C#
Q wrapper for the Interactive Brokers API
-
Updated
Jan 14, 2019 - C++
Utilities to automate small daily tasks for algo traders.
-
Updated
Dec 29, 2019 - Python
"High Frequency" style trading algo based on the Dempster-Shafer fusion theory in C# using the Interactive Brokers API.
trading-bot
depth
trading-algorithms
hft-trading
bid
interactive-brokers
dempster-shafer-theory
price-improvement-degree
mass-functions
style-trading-algo
-
Updated
Apr 27, 2019 - C#
Demo configuration files and strategy code for QuantRocket
-
Updated
May 22, 2020 - Jupyter Notebook
An R implementation of Interactive Brokers API
-
Updated
May 7, 2020 - R
Improve this page
Add a description, image, and links to the interactive-brokers topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the interactive-brokers topic, visit your repo's landing page and select "manage topics."
According last Travis build
https://travis-ci.org/ranaroussi/qtpylib/jobs/214950579
there's currently no unit tests maybe you should add some unit tests
to ensure that coding new feature doesn't break existing code