Skip to content

Trade history

The history is the list of all finished trades: from signals, manual ones and the trades of DCA bots. From here you can open the card of any closed trade and download the history as a file. The trades themselves are never deleted, so the history is available for any period.

Where it is in the bot

Main menu → 💼 TradesHistory. The screen shows the “Filters” block with the lines “Selected time period:” and “Selected trading pair:”, and below it the list and the trade buttons. Open trades do not appear in the history — they are in the “Active trades” list.

How it works

The quick filters

  1. Choose the period with a button: today, yesterday, last 3 days, last week, last 2 weeks, last month or all time.
  2. The bot asks: “Choose which trading pair you want to view history for the selected period”. Pick a pair or press All currencies to show them all.
  3. The list “Your trades for the selected period” appears with the line “Closed trades: 37”. The trades are grouped by bot; each one shows the direction and the pair with the opening date, then “id: 1403 • Completed (TP)”, “Closed: …” and “💰 PnL: …”. The trade buttons are labelled with the direction and the pair. New trades are on top, a long list is split into pages.
  4. Press a trade button and “Completed trade information” opens: the same fields as in the card of an open trade, plus the final status and the line “💰 PnL: +12.40 USDT (+2.48%)” — the result of the closed trade.

The custom filter

The Custom filter button accepts a text in one of three forms:

FormExampleWhat it selects
Dates only01.01.2026-31.01.2026All the trades closed in January
Dates and a pair01.01.2026-31.01.2026-BTC/USDTThe January trades on BTC/USDT
Extendedperiod=01.01.2026-31.01.2026 pair=BTC/USDT direction=LONG result=PROFIT bot=MyBotAny combination of the fields

The fields of the extended form:

FieldValues
periodFROM-TO, the dates in the format dd.MM.yyyy
pairA pair such as BTC/USDT
directionLONG or SHORT
resultPROFIT, LOSS or BREAK (break even)
botThe name of your bot, as it is in its card

The fields can be used in any combination — for example, only result=LOSS bot=MyBot to see all the losing trades of one bot. The bot answers “Custom filter applied:” and shows “Your trades by selected filters”.

What the status labels mean

In the list the status has a short label: “Completed (TP)”, “Completed (SL)”, “Cancelled”, “Cancelled during opening”, “Failed to place orders”, “Cancelled by system (14+ days without activity)”, “💥 Liquidated by the exchange”, “🎯 Cancelled by trigger (target hit before entry)”. They are explained in the article Trade statuses.

Export

On the history screen there is the 📥 Export CSV button — it downloads all the closed trades as a single file, regardless of the filters you selected. The command /export_history does the same. More on this in Exporting the history to CSV.

Statistics by channel

The totals for the trades from each connected channel — how many closed by TP, by SL, were cancelled and what the WinRate is — are shown by the screen Main menu → 📡 Signals. This is the statistics of your own finished trades, not the theoretical statistics of the channel signals.

Limits and allowed values

ParameterValue
The date format in a filterdd.MM.yyyy, a range through a hyphen
DirectionLONG, SHORT
ResultPROFIT, LOSS, BREAK
Keeping the tradesNever deleted; the history is available for all time

Common errors and what the bot says

  • “You have no trades for the selected period” — nothing was closed in that period; widen the period.
  • “You have no trades matching the search criteria” — no trade matched the custom filter.
  • “Invalid filter format. Use: dd.MM.yyyy-dd.MM.yyyy[-BTC/USDT] or DSL (period=, pair=, direction=, result=, bot=)” — check the spelling, the dates go through a hyphen without spaces.
  • “Could not parse dates. Format: dd.MM.yyyy (e.g. 01.01.2026)”.
  • “Could not find this trading pair. Use format BTC/USDT”.
  • “Invalid direction. Allowed: LONG, SHORT”.
  • “Invalid result. Allowed: PROFIT, LOSS, BREAK”.
  • “Bot with this name was not found” — the name in bot= must match the name of the bot in its card.