How to Build a Weekly Trading Review with the TradeTally API

A weekly review becomes difficult to compare when each recap uses a different date range, data source, or structure. This guide shows how to assemble a repeatable summary with TradeTally API data, including weekly analytics, dated diary entries, trade-level setup tags and P&L, and setup-level edge results.

The focus is on automated reporting inputs and organization, not financial advice. Before implementing requests, confirm endpoint details and available fields in the TradeTally API Documentation.

What a weekly trading review should collect

Start by defining the review as a summary of one selected week rather than a manual recap of individual trades. A fixed reporting period gives each run the same boundary and makes the returned sections easier to compare.

The TradeTally data sources for this structure are specific:

• The /api/analytics endpoint returns weekly and monthly performance breakdowns.
• Trade records include setup tags and P&L per trade.
• Diary entries are available through /api/diary, linked by date and filterable by date range.
• The edge report endpoint surfaces setup-level win rates, profit factors, and sample counts.

Your report can present these sources as separate sections instead of treating the weekly review as one undifferentiated result.

Weekly trading review automation: choose the reporting inputs

Set the reporting period before requesting data. For example, decide that the report covers Monday through Sunday, then use that same date range when working with the weekly review’s analytics and diary data.

Use /api/analytics for the weekly performance breakdown. The endpoint returns weekly and monthly performance breakdowns, but the API documentation should be the authority for request details, parameters, authentication, and response fields. Avoid building assumptions around fields that are not documented.

Next, retain the setup tag and P&L for each trade in the trade-level portion of the report. This gives the weekly summary a direct trade-record basis while preserving the label needed for setup-level organization.

Pull dated diary entries alongside trade results

Request diary entries through /api/diary and filter them by the same date range used for the weekly review. Since diary entries are linked by date, keep the date visible when presenting each entry alongside the rest of the week’s information.

A simple report layout might place the weekly performance breakdown first, followed by dated diary entries and the trade list. This keeps the journal content associated with the period in which it was recorded rather than detaching it from the week’s results.

For additional context on timely journal work, see the End of Day Trading Journal guide. That context does not mean the API automatically creates diary entries; the implementation described here reads entries through /api/diary.

Group the weekly summary by setup tag

Preserve every trade’s setup tag when organizing the output. A setup-grouped view can show which trades belong to each label while retaining the individual P&L values used in the trade list.

Do not replace setup information with additional indicators unless those indicators exist in your own data. The supported TradeTally fact for this workflow is that trade records include setup tags. The label is therefore the stable grouping field supplied by the trade record.

The article Trading Setup Tags: Why They Matter More Than Tracking More Indicators provides focused context for using setup labels in review work.

Add setup-level context with the edge report endpoint

Use the edge report endpoint to add setup-level win rates, profit factors, and sample counts to the weekly review. Keep these results distinct from the individual trade list: one section describes trades, while the edge report provides setup-level values.

Always display the sample count beside the corresponding setup-level results. For a reader reviewing the output, the count is part of the returned context and should not be separated from the win rate or profit factor.

For a practical discussion of turning setup data into one weekly review action, read the Trading Edge Report article. This article stays focused on assembling the returned data into a repeatable report.

Worked example: a hypothetical weekly output

Assume, purely hypothetically, that the selected week contains 12 trades. Four trades have the setup tag Breakout, five have Pullback, and three have Range. The trade section would list each trade’s setup tag and P&L, while the setup section would show the edge report’s returned win rate, profit factor, and sample count for each setup.

• Breakout: sample count 4, with a hypothetical win rate of 50% and hypothetical profit factor of 1.20.
• Pullback: sample count 5, with a hypothetical win rate of 60% and hypothetical profit factor of 1.35.
• Range: sample count 3, with a hypothetical win rate of 33% and hypothetical profit factor of 0.80.

These numbers are illustrative only. They are not TradeTally results, trading guidance, or a prediction; they show how to keep each setup’s reported metrics next to its sample count while the trade list preserves the underlying setup tags and P&L.

Protect an external reporting workflow with read-only permissions

If an external reporting tool will read the weekly data, create an API key with read-only permissions. TradeTally API key permissions can be scoped to read-only for external reporting tools, which keeps the key’s stated purpose aligned with reading analytics, diary entries, trade records, and edge-report data.

Manage access through TradeTally API keys. The TradeTally Features page can provide broader product context, while the API documentation should guide the implementation itself.

Keep the reporting process focused on the supported reading use case. Do not assume that a read-only key performs write actions or creates diary entries.

Turn the returned data into a repeatable weekly report

Define the report structure once and use it for each selected week. A practical fixed structure is:

1. Weekly performance: the breakdown returned by /api/analytics.
2. Trade list: each trade’s setup tag and P&L.
3. Diary entries: entries from /api/diary filtered to the same date range and shown with their dates.
4. Setup-level results: win rates, profit factors, and sample counts from the edge report endpoint.

Have the reporting process output these sections in the same order each week. The goal is consistency in presentation: the underlying data can change, but the reader should know where to find each returned value.

For more API context, see TradeTally trading journal API: From CSV imports to programmable trade analytics. Keep this workflow limited to the supplied endpoint facts and fields rather than adding unsupported calculations.

FAQ: Weekly trading review automation with the TradeTally API

Can the TradeTally API return weekly performance data?

Yes. The /api/analytics endpoint returns weekly and monthly performance breakdowns. Check the API documentation for the request and response details before implementing the report.

How can I retrieve journal notes for one week?

Use /api/diary and filter diary entries by the selected date range. Diary entries are linked by date, so retain the date when presenting them in the weekly summary.

Can I review performance by trading setup?

Yes. Trade records include setup tags, and the edge report endpoint surfaces setup-level win rates, profit factors, and sample counts. Keep the sample count beside the other setup-level results.

What permission should an external reporting tool use?

API key permissions can be scoped to read-only for external reporting tools. Use a read-only scope when the tool’s purpose is to read the weekly analytics, diary, trade, and edge-report data used in the summary.

Ready to build the workflow? Create a scoped TradeTally API key, then review the API documentation before implementing your weekly reporting process.