Skip to main content

IBKR Authentication Workflow

PyPI - Version PyPI - Downloads Codecov

Interactive Brokers provides an extensive API that can be used for trading and account management.

It's also possible to authenticate for the API via OAuth.

ibauth is a Python client for handling the full Interactive Brokers (IBKR) Web API authentication flow. It wraps the OAuth2 + session lifecycle steps (access_token, bearer_token, ssodh_init, tickle, etc.) into a simple, reusable interface.

🔑 Features:

  • Obtain and refresh IBKR OAuth2 tokens.
  • Manage brokerage sessions (ssodh_init, validate_sso, tickle, logout).
  • YAML-based configuration (easy to keep credentials outside of code).
  • Logging of requests and responses for troubleshooting.

Documentation for the IBKR Web API can be found in the official reference.


Requirements

  • Python 3.11+
  • A valid IBKR account with Web API access enabled.
  • An RSA private key (.pem) registered with IBKR.

Installation

You can install either from PyPI (preferred) or GitHub (which may give access to updates not yet published on PyPI).

# Install from PyPI.
uv add ibauth
pip install ibauth

# Install from GitHub.
uv add "git+https://github.com/datawookie/ibkr-oauth-flow"
pip install "git+https://github.com/datawookie/ibkr-oauth-flow"

Getting Started

The package implements authentication via the IBAuth class. There are two approaches to instantiating this class:

  • directly via the constructor or
  • using the auth_from_yaml() factory function.

Authenticator Objects

Instantiate a IBAuth object (illustrative values for constructor parameters):

from ibauth import IBAuth

auth = IBAuth(
  client_id = "Authenticator-Client",
  client_key_id = "main",
  credential = "DiV7hxH5yXAN5x",
  private_key_file = "/path/to/ibkr-private-key.pem",
)

where

  • client_id — client ID;
  • client_key_id — key identifier associated with your private key;
  • credential — credential string; and
  • private_key_file — path to your RSA private key (.pem).

There are optional arguments:

  • timeout — timeout (seconds) applied to all network requests.

Configuration File

A more flexible approach is to create a YAML configuration file rather than baking those values into your code. You can copy config.example.yaml to config.yaml and fill in your credentials. The file might look something like this:

client_id: "Authenticator-Client"
client_key_id: "main"
credential: "DiV7hxH5yXAN5x"
private_key_file: "/path/to/ibkr-private-key.pem"

Then use the factory function:

from ibauth import auth_from_yaml

auth = auth_from_yaml("config.yaml")

Methods

Use the following public methods:

  • connect() — run the authentication flow to connect to the API; and
  • tickle() — keep the API connection alive.

Attributes

These are some useful attributes:

  • bearer_token — the bearer token acquired during the authentication flow;
  • header — the authentication header (as a dictionary);
  • authenticated — are we authenticated?;
  • connected — are we connected?; and
  • competing — is there a competing connection?

The authenticated, connected and competing attributes are set and updated by running the tickle() method.

Development

Clone the repo and install dependencies into a virtual environment:

git clone https://github.com/datawookie/ibkr-oauth-flow.git
cd ibkr-oauth-flow
uv sync

You can test the authentication workflow:

# Use config.yaml in current directory.
uv run ibauth
# Use config.yaml in home directory and include debugging output.
uv run ibauth --config ~/config.yaml --debug

Test Suite

This project uses pytest. To run the test suite:

uv run pytest

To include coverage:

uv run pytest --cov=.

Deploy to PyPI

This requires UV_PUBLISH_TOKEN to be set to a PyPi token in environment.

make deploy

Metadata

Release files for ibauth 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ibauth 0.1.6
File Size Uploaded Provenance Actions
ibauth-0.1.6.tar.gz 15.0 kB Without provenance Details for ibauth-0.1.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ibauth 0.1.6
File Interpreter ABI Platform Actions
ibauth-0.1.6-py3-none-any.whl Python 3 none any Details for ibauth-0.1.6-py3-none-any.whl

Total release size: 26.4 kB

Release files / ibauth-0.1.6.tar.gz

Download URL ibauth-0.1.6.tar.gz
Size 15.0 kB
Tags Source
SHA-256 checksum
How to use checksums
9a6e1e9bd3c4c44646badf563a67f5ca0158f45a3589358e164bf4949644ca26
BLAKE2b-256 checksum
How to use checksums
bba7f5c2937393607ad363f82a27b95c2a93db8276581895a64b822e432c0c11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / ibauth-0.1.6-py3-none-any.whl

Download URL ibauth-0.1.6-py3-none-any.whl
Size 11.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
265615f96b2d840611f5f4c84586e9a2a670d61398bcd1f9f169d586309dd9b7
BLAKE2b-256 checksum
How to use checksums
4fd9f8bcb4eb87e2d545bee8aa27c1ca6f627db34403248341451d3f87891213
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for ibauth 0.1.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page