Crates.io | ibapi |
lib.rs | ibapi |
version | 1.0.5 |
source | src |
created_at | 2023-04-08 07:08:54.918734 |
updated_at | 2024-12-10 20:17:07.390631 |
description | A Rust implementation of the Interactive Brokers TWS API, providing a reliable and user friendly interface for TWS and IB Gateway. Designed with a focus on simplicity and performance. |
homepage | https://github.com/wboayue/rust-ibapi/ |
repository | https://github.com/wboayue/rust-ibapi/ |
max_upload_size | |
id | 833473 |
size | 878,780 |
This library provides a comprehensive Rust implementation of the Interactive Brokers TWS API, offering a robust and user-friendly interface for TWS and IB Gateway. Designed with performance and simplicity in mind, ibapi
is a good fit for automated trading systems, market analysis, real-time data collection and portfolio management tools.
With this fully featured API, you can retrieve account information, access real-time and historical market data, manage orders, perform market scans, and access news and Wall Street Horizons (WSH) event data. Future updates will focus on bug fixes, maintaining parity with the official API, and enhancing usability.
If you encounter any issues or require a missing feature, please review the issues list before submitting a new one.
The Client documentation provides comprehensive details on all currently available APIs, including trading, account management, and market data features, along with examples to help you get started.
Check crates.io/crates/ibapi for the latest available version and installation instructions.
These examples demonstrate key features of the ibapi
API.
The following example shows how to connect to TWS.
use ibapi::Client;
fn main() {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, 100).expect("connection to TWS failed!");
println!("Successfully connected to TWS at {connection_url}");
}
Note: Use
127.0.0.1
instead oflocalhost
for the connection. On some systems,localhost
resolves to an IPv6 address, which TWS may block. TWS only allows specifying IPv4 addresses in the allowed IP addresses list.
Here’s how to create a stock contract for TSLA using the stock helper function.
// Create a contract for TSLA stock (default currency: USD, exchange: SMART)
let contract = Contract::stock("TSLA");
The stock, futures, and crypto methods provide shortcuts for defining contracts with reasonable defaults that can be modified after creation.
For contracts requiring custom configurations:
// Create a fully specified contract for TSLA stock
Contract {
symbol: "TSLA",
security_type: SecurityType::Stock,
currency: "USD".to_string(),
exchange: "SMART".to_string(),
..Default::default()
}
For a complete list of contract attributes, explore the Contract documentation.
The following is an example of requesting historical data from TWS.
use time::macros::datetime;
use ibapi::contracts::Contract;
use ibapi::market_data::historical::{BarSize, ToDuration, WhatToShow};
use ibapi::Client;
fn main() {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, 100).expect("connection to TWS failed!");
let contract = Contract::stock("AAPL");
let historical_data = client
.historical_data(
&contract,
datetime!(2023-04-11 20:00 UTC),
1.days(),
BarSize::Hour,
WhatToShow::Trades,
true,
)
.expect("historical data request failed");
println!("start: {:?}, end: {:?}", historical_data.start, historical_data.end);
for bar in &historical_data.bars {
println!("{bar:?}");
}
}
The following is an example of requesting realtime data from TWS.
use ibapi::contracts::Contract;
use ibapi::market_data::realtime::{BarSize, WhatToShow};
use ibapi::Client;
fn main() {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, 100).expect("connection to TWS failed!");
// Request real-time bars data for AAPL with 5-second intervals
let contract = Contract::stock("AAPL");
let subscription = client
.realtime_bars(&contract, BarSize::Sec5, WhatToShow::Trades, false)
.expect("realtime bars request failed!");
for bar in subscription {
// Process each bar here (e.g., print or use in calculations)
println!("bar: {bar:?}");
}
}
In this example, the request for realtime bars returns a Subscription that is implicitly converted into a blocking iterator over the bars. The subscription is automatically cancelled when it goes out of scope. The Subscription
can also be used to iterate over bars in a non-blocking fashion.
// Example of non-blocking iteration
loop {
match subscription.try_next() {
Some(bar) => println!("bar: {bar:?}"),
None => {
// No new data yet; perform other tasks or sleep
std::thread::sleep(Duration::from_millis(100));
}
}
}
Explore the Subscription documentation for more details.
Since subscriptions can be converted to iterators, it is easy to iterate over multiple contracts.
use ibapi::contracts::Contract;
use ibapi::market_data::realtime::{BarSize, WhatToShow};
use ibapi::Client;
fn main() {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, 100).expect("connection to TWS failed!");
// Request real-time bars data for AAPL with 5-second intervals
let contract_aapl = Contract::stock("AAPL");
let contract_nvda = Contract::stock("NVDA");
let subscription_aapl = client
.realtime_bars(&contract_aapl, BarSize::Sec5, WhatToShow::Trades, false)
.expect("realtime bars request failed!");
let subscription_nvda = client
.realtime_bars(&contract_nvda, BarSize::Sec5, WhatToShow::Trades, false)
.expect("realtime bars request failed!");
for (bar_aapl, bar_nvda) in subscription_aapl.iter().zip(subscription_nvda.iter()) {
// Process each bar here (e.g., print or use in calculations)
println!("AAPL {}, NVDA {}", bar_aapl.close, bar_nvda.close);
}
}
Note: When using
zip
, the iteration will stop if either subscription ends. For independent processing, consider handling each subscription separately.
pub fn main() {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, 100).expect("connection to TWS failed!");
let contract = Contract::stock("AAPL");
// Creates a market order to purchase 100 shares
let order_id = client.next_order_id();
let order = order_builder::market_order(Action::Buy, 100.0);
let subscription = client.place_order(order_id, &contract, &order).expect("place order request failed!");
for event in &subscription {
if let PlaceOrder::ExecutionData(data) = event {
println!("{} {} shares of {}", data.execution.side, data.execution.shares, data.contract.symbol);
} else {
println!("{:?}", event);
}
}
}
The Client can be shared between threads to support concurrent operations. The following example demonstrates valid multi-threaded usage of Client.
use std::sync::Arc;
use std::thread;
use ibapi::contracts::Contract;
use ibapi::market_data::realtime::{BarSize, WhatToShow};
use ibapi::Client;
fn main() {
let connection_url = "127.0.0.1:4002";
let client = Arc::new(Client::connect(connection_url, 100).expect("connection to TWS failed!"));
let symbols = vec!["AAPL", "NVDA"];
let mut handles = vec![];
for symbol in symbols {
let client = Arc::clone(&client);
let handle = thread::spawn(move || {
let contract = Contract::stock(symbol);
let subscription = client
.realtime_bars(&contract, BarSize::Sec5, WhatToShow::Trades, false)
.expect("realtime bars request failed!");
for bar in subscription {
// Process each bar here (e.g., print or use in calculations)
println!("bar: {bar:?}");
}
});
handles.push(handle);
}
handles.into_iter().for_each(|handle| handle.join().unwrap());
}
Some TWS API calls do not have a unique request ID and are mapped back to the initiating request by message type instead. Since the message type is not unique, concurrent requests of the same message type (if not synchronized by the application) may receive responses for other requests of the same message type. Subscriptions using shared channels are tagged with the SharesChannel trait to highlight areas that the application may need to synchronize.
To avoid this issue, you can use a model of one client per thread. This ensures that each client instance handles only its own messages, reducing potential conflicts:
use std::thread;
use ibapi::contracts::Contract;
use ibapi::market_data::realtime::{BarSize, WhatToShow};
use ibapi::Client;
fn main() {
let symbols = vec![("AAPL", 100), ("NVDA", 101)];
let mut handles = vec![];
for (symbol, client_id) in symbols {
let handle = thread::spawn(move || {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, client_id).expect("connection to TWS failed!");
let contract = Contract::stock(symbol);
let subscription = client
.realtime_bars(&contract, BarSize::Sec5, WhatToShow::Trades, false)
.expect("realtime bars request failed!");
for bar in subscription {
// Process each bar here (e.g., print or use in calculations)
println!("bar: {bar:?}");
}
});
handles.push(handle);
}
handles.into_iter().for_each(|handle| handle.join().unwrap());
}
In this model, each client instance handles only the requests it initiates, improving the reliability of concurrent operations.
The API will automatically attempt to reconnect to the TWS server if a disconnection is detected. The API will attempt to reconnect up to 30 times using a Fibonacci backoff strategy. In some cases, it will retry the request in progress. When receiving responses via a Subscription, the application may need to handle retries manually, as shown below.
use ibapi::contracts::Contract;
use ibapi::market_data::realtime::{BarSize, WhatToShow};
use ibapi::{Client, Error};
fn main() {
let connection_url = "127.0.0.1:4002";
let client = Client::connect(connection_url, 100).expect("connection to TWS failed!");
let contract = Contract::stock("AAPL");
loop {
// Request real-time bars data with 5-second intervals
let subscription = client
.realtime_bars(&contract, BarSize::Sec5, WhatToShow::Trades, false)
.expect("realtime bars request failed!");
for bar in &subscription {
// Process each bar here (e.g., print or use in calculations)
println!("bar: {bar:?}");
}
if let Some(Error::ConnectionReset) = subscription.error() {
eprintln!("Connection reset. Retrying stream...");
continue;
}
break;
}
}
We welcome contributions of all kinds. Feel free to propose new ideas, share bug fixes, or enhance the documentation. If you'd like to contribute, please start by reviewing our contributor documentation.
For questions or discussions about contributions, feel free to open an issue or reach out via our GitHub discussions page.