# ib-api-reloaded/ib_async

Python sync/async framework for Interactive Brokers API (replaces ib_insync)

Repository: https://github.com/ib-api-reloaded/ib_async
Canonical: https://ross.abutalabs.com/products/ib_async
Language: Python
License: BSD-2-Clause
License Family: permissive
Topics: ib-insync, ibkr, interactive-brokers, interactive-brokers-api, trading, twsapi, ib-async
Last push: 2026-08-19T03:04:44+00:00

## Health v2 (maintenance only)
Score: 60/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 8, longevity 64
- inputs: {"age_days": 902, "days_push": 14, "days_rel": 437, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1723, forks 250 (observed 2026-08-28T04:05:27.919150+00:00)

## What it is
ib_async is a Python library providing a clean sync/async interface to Interactive Brokers' Trader Workstation (TWS) API and IB Gateway, succeeding the popular ib_insync. It handles connection management, automatic state synchronization, and reconnection so developers can build trading, market data, and portfolio applications.

## Use cases
- stream live market quotes and historical data from Interactive Brokers
- place, modify, and monitor stock and option orders programmatically
- track portfolio positions, account balances, and P&L in real time
- analyze option chains and contract details for research
- build automated trading bots on IBKR
- monitor risk exposures with automated controls
- explore IBKR data interactively in Jupyter notebooks

## When to choose
- you trade through Interactive Brokers and want a Pythonic API instead of the raw TWS API
- you need both synchronous and asyncio-based access to IBKR
- you're migrating from ib_insync and want a maintained successor
- you want interactive IBKR data exploration in Jupyter

## When to avoid
- you trade with a different broker than Interactive Brokers
- you need a broker-agnostic trading abstraction layer
- you can't run TWS or IB Gateway alongside your application
- you need a full backtesting or strategy framework rather than a broker API client

## Facets
- artifact type: library
- maturity: active
- function: sdk, http-client, concurrency, streaming
- domain: fintech, apis, developer-tools
- platform: python, cross-platform
- tags: interactive-brokers, ibkr, trading-api, asyncio, market-data, order-execution, ib-insync-successor, trading

## Member repositories
- ib-api-reloaded/ib_async (main) score 60

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:27.919150+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:33:58.115292+00:00, confidence not recorded.
  - readme: https://github.com/ib-api-reloaded/ib_async (fetched 2026-08-28T04:05:27.919150+00:00, sha 901898d27dc4)
  - registry_pypi: https://pypi.org/pypi/ib_async/json (fetched 2026-08-29T11:09:27.341351+00:00, sha 65845ed4e22e)
- Data as of 2026-08-30T08:39:29.467469+00:00.