Tradier

This is a guide for using Tradier with the Lumibot library.

Getting Started

To get started, you will need to create a Tradier account and get your Account Number and API Secret. You can do this by visiting the [Tradier website](https://www.tradier.com/).

Once you have an account and you’ve logged in you can find your Account Number and API Secret by visiting the [API Access page](https://dash.tradier.com/settings/api).

Note

Easy Setup with .env File

LumiBot automatically loads your API credentials from a .env file! Simply create a .env file in the same folder as your trading strategy and add your Tradier credentials. LumiBot will automatically detect and use these credentials - no additional configuration required.

Example .env file:

# Tradier Configuration
TRADIER_ACCESS_TOKEN=your_access_token_here
TRADIER_ACCOUNT_NUMBER=your_account_number_here
TRADIER_IS_PAPER=true

That’s it! LumiBot handles the rest automatically.

For Tradier OAuth integrations, use TRADIER_TOKEN_PATH instead of placing the token payload directly in your strategy code. The file should contain a provider token JSON payload with fields such as access_token, refresh_token, expires_in, and issued_at. When LumiBot refreshes the OAuth token, it writes the updated payload back to the same file. If that write fails, LumiBot fails the refresh rather than pretending the new token was durable.

Configuration

Here is an example dictionary of configuration options for Tradier:

TRADIER_CONFIG = {
    # Put your own Tradier key here:
    "ACCESS_TOKEN": "qTRz3zUrd9244AHUw2AoyAPgvYra",
    # Put your own Tradier account number here:
    "ACCOUNT_NUMBER": "VA22904793",
    # If you want to use real money you must change this to False
    "PAPER": True,
}

or more generally:

TRADIER_CONFIG = {
    "ACCESS_TOKEN": "your_access_token",
    "ACCOUNT_NUMBER": "your_account_number",
    "PAPER": True,
}

For OAuth token-file usage, set the account and paper/live mode as usual, then point LumiBot at the provider token file:

TRADIER_TOKEN_PATH=/secure/path/tradier_token.json
TRADIER_ACCOUNT_NUMBER=your_account_number
TRADIER_IS_PAPER=true
TRADIER_OAUTH_CLIENT_ID=your_oauth_client_id
TRADIER_OAUTH_CLIENT_SECRET=your_oauth_client_secret

TRADIER_ACCESS_TOKEN remains supported for manual API-token users. The token file path is for OAuth flows that need refresh-token durability.

Running Your Strategy

To run your strategy, you’ll first need to instantiate your chosen broker with the correct configuration:

from lumibot.brokers import Tradier

broker = Tradier(config=TRADIER_CONFIG)

Then you can run your strategy as you normally would:

from lumibot.trader import Trader

strategy = MyStrategy(broker=broker) # Your normal strategy class, with on_trading_iteration, etc
trader = Trader()
trader.add_strategy(strategy)
strategy_executors = trader.run_all()

That’s it! You should now be able to run your strategy using Tradier as your broker.

Full Example Strategy

Here is an example of a simple strategy that uses Tradier as the broker:

from lumibot.brokers import Tradier
from lumibot.trader import Trader
from lumibot.strategies import Strategy

TRADIER_CONFIG = {
    "ACCESS_TOKEN": "your_access_token",
    "ACCOUNT_NUMBER": "your_account_number",
    "PAPER": True,
}

class MyStrategy(Strategy):
    def on_trading_iteration(self):
        # Buy 1 share of AAPL if the price is less than $100
        price = self.get_last_price("AAPL")
        self.log_message(f"AAPL price: {price}")

broker = Tradier(config=TRADIER_CONFIG)
strategy = MyStrategy(broker=broker)
trader = Trader()
trader.add_strategy(strategy)
strategy_executors = trader.run_all()

Cash Events

Lumibot can emit normalized live cash_events in the cloud payload for Tradier strategies. These events are pulled from Tradier account history and are separate from LumiBot’s order lifecycle pipeline.

Supported history categories include:

  • ACH and wire activity

  • dividends

  • interest

  • fees and taxes

  • journals

  • checks, transfers, and adjustments

Normalized cash-event shape

Each emitted event includes:

  • event_id (stable deterministic ID for downstream idempotency)

  • broker_event_id (when Tradier provides one)

  • broker_name

  • event_type

  • raw_type

  • raw_subtype

  • amount

  • currency

  • occurred_at

  • description

  • direction

  • is_external_cash_flow

Tradier-specific limitations

  • Tradier account history is a broker history surface, not a real-time stream.

  • Tradier’s official API only exposes account history for live accounts.

  • Tradier sandbox/paper accounts do not provide account history, so the cash-event read path cannot be fully smoke tested against paper credentials.

  • Tradier history is updated on a delayed/nightly basis, so new cash events are not expected to appear intraday.

See also: Cash Accounting