Trading Journal API: From Broker CSV Imports to TradeTally Analytics

If you already import broker CSV files into a trading journal, the next question is usually practical: what can you query after the data is inside the system? This article focuses on the TradeTally trading journal API facts that matter for programmatic review: imported trades, available fields, filters, full P&L fields, and precomputed analytics.

This is not about broker execution, real-time sync, market prediction, or financial advice. It is a narrow map of what TradeTally exposes through its API after CSV import.

Start with the broker data TradeTally can import

Before planning any API-based analysis, confirm whether your broker is in TradeTally’s supported CSV import list. The API is most useful when the trade history you want to query can first be imported into the journal.

TradeTally supports CSV imports from Lightspeed, Schwab, thinkorswim, IBKR, Webull, E*TRADE, Tradovate, Questrade, TradeStation, tastytrade, and more. If your immediate project is moving prior broker records into a journal, see Import Trade History to Trading Journal: Move Years of Broker History Without Manual Entry.

Keep the scope clear. CSV import gets the broker trade history into TradeTally. After import, the REST API makes those trades available with full P&L fields.

What a trading journal API exposes after import

Make a field checklist before you write queries. That keeps your programmatic review aligned with the trade attributes TradeTally makes available.

After import, trades are available through the TradeTally REST API with full P&L fields. Each trade includes broker, symbol, side, quantity, entry price, exit price, dates, and tags.

Data area	Available through TradeTally API facts	How to use it in planning
Source	Broker	Separate records by imported broker source.
Instrument	Symbol	Review trades for one symbol or compare symbol-level slices outside the API response.
Trade direction and size	Side and quantity	Include direction and position size fields in your trade record checklist.
Prices	Entry price and exit price	Inspect imported trade pricing fields programmatically.
Timing	Dates	Build date-based review periods using available date fields.
Labels	Tags	Query and inspect trades associated with specific tags.
Results	Full P&L fields	Include P&L data in trade-level review.

These fields are useful for programmatic review because you can query structured trade records rather than manually reading CSV rows. For endpoint details and implementation specifics, use the TradeTally API Documentation.

Use /api/trades filters to narrow the dataset before analysis

Decide the filter you need before writing the request. The /api/trades endpoint supports filtering by date range, broker, symbol, and tag.

A date range can focus the dataset on a specific review period. A broker filter can separate imported histories when you have more than one broker source in the journal.

A symbol filter can narrow the response to one market. A tag filter can inspect trades labeled with a specific tag.

For example, suppose you hypothetically imported 250 trades from IBKR and 180 trades from Schwab. You want to review only March trades from IBKR for AAPL that were labeled with a “breakout” tag.

1. Set the date range to the March review period.
2. Set the broker filter to IBKR.
3. Set the symbol filter to AAPL.
4. Set the tag filter to “breakout.”
5. Review the returned trade records for fields such as broker, symbol, side, quantity, entry price, exit price, dates, tags, and full P&L fields.

The numbers in that example are hypothetical. The important point is the sequence: define the slice first, then query only the trade records relevant to that review.

This article does not assume details that are not included in the supplied TradeTally facts. It does not describe pagination, sorting, authentication, webhooks, order execution, or real-time broker sync. For a related API-focused article, see TradeTally trading journal API: From CSV imports to programmable trade analytics.

Pull precomputed analytics instead of recalculating every summary from raw trades

Before building your review, identify whether you need trade-level records, summary analytics, or both. TradeTally exposes imported trades through the REST API, and analytic summaries including expectancy and profit factor are precomputed and available via API.

That means expectancy and profit factor are available as API-accessible review metrics. They should not be treated as buy or sell signals, and they are not financial advice.

A simple API planning note might separate the work into two categories. First, request trade records when you need broker, symbol, side, quantity, prices, dates, tags, and full P&L fields. Second, use the API-available analytic summaries when you need values such as expectancy and profit factor.

If you are designing a recurring review document around API-accessible data, Trading Journal API: Build a Weekly Trading Review with TradeTally is a related planning resource.

Plan a simple API review workflow around supported fields only

A practical way to avoid overbuilding is to outline your programmatic review in three parts: imported broker source, trade filters, and analytics to request. This keeps the plan tied to fields and summaries TradeTally explicitly exposes.

1. Broker source: list the broker or brokers imported by CSV, such as Lightspeed, Schwab, thinkorswim, IBKR, Webull, E*TRADE, Tradovate, Questrade, TradeStation, or tastytrade.
2. Trade filters: decide whether the /api/trades request should be narrowed by date range, broker, symbol, tag, or a combination of those filters.
3. Fields and analytics: decide whether you need trade-level fields, full P&L fields, and precomputed summaries such as expectancy and profit factor.

Here is a compact worked example using hypothetical review notes:

Planning item	Hypothetical choice	TradeTally fact used
Imported source	IBKR CSV import	TradeTally supports CSV imports from IBKR.
Review period	April 1 through April 30	/api/trades supports filtering by date range.
Market slice	MSFT trades	/api/trades supports filtering by symbol.
Label slice	Trades tagged “pullback”	/api/trades supports filtering by tag.
Record fields	Side, quantity, entry price, exit price, dates, tags, full P&L fields	Each trade includes those trade attributes, and imported trades are available with full P&L fields.
Summary metrics	Expectancy and profit factor	Analytic summaries including expectancy and profit factor are precomputed and available via API.

This structure does not assume a specific script, language, output format, or reporting destination. It simply translates the available TradeTally API facts into a checklist you can use before implementation.

If you are comparing journaling requirements more broadly, review the TradeTally Features page or the trading journal software comparison checklist.

FAQ: Trading journal API questions from CSV-importing traders

Can I import broker trades by CSV and then query them through the API?

Yes. TradeTally supports CSV imports from brokers including Lightspeed, Schwab, thinkorswim, IBKR, Webull, E*TRADE, Tradovate, Questrade, TradeStation, tastytrade, and more. After import, trades are available via the REST API with full P&L fields.

What fields can I query for each imported trade?

Each trade includes broker, symbol, side, quantity, entry and exit prices, dates, and tags. Imported trades are also available through the REST API with full P&L fields.

Can I filter imported trades through the API?

Yes. The /api/trades endpoint supports filtering by date range, broker, symbol, and tag.

Are analytics available through the API, or only raw trades?

Analytic summaries including expectancy and profit factor are precomputed and available via API. These are review metrics exposed through the API, not trading recommendations.

Where should I go for implementation details?

Use the TradeTally API Documentation for implementation details. This article is a practical scope map, not a replacement for the API reference.

Ready to inspect the API directly? Open the TradeTally API Documentation and use it to plan your CSV-import-to-query workflow around supported fields, filters, and analytics.