Bitget trade journal

Bitget Trade Journal — Auto-Import Your Trades

Bitget runs spot and USDT-margined perpetual futures and is widely used for copy trading. Its API keys require a passphrase set at creation, which Trnd Tools stores alongside the key and secret and sends only when an import runs.

Start journaling free

Free for up to 10 trades a month. Includes 30 days of Pro, no card required.

How the Bitget sync works

Four steps, about five minutes. The key you create only ever reads trade history.

1
Create a read-only API key on Bitget
When creating the key on Bitget, choose "Read-only" rather than "Read-write", and set the passphrase Bitget requires. A read-only key cannot place orders or withdraw. Bitget also asks you to set a passphrase for the key - keep it, the connect form needs it too. Trnd Tools never needs trading or withdrawal permission.
2
Paste the key into Trnd Tools
Open the journal, choose Bitget in Connect Exchange, paste the API key and secret and the passphrase, and tick the confirmation that the key is read-only. The server refuses any connection without that confirmation.
3
Choose a ledger
Pick which ledger the trades should land in - one per account or strategy, or a single ledger for everything. Each connection can be imported into a different ledger.
4
Import
Click Sync now. Trnd Tools fetches your fills, builds closed positions from them and files them in a ledger named after the connection. From then on new trades are pulled in automatically every hour.

Copy-trading positions are executed on your own account, so the fills they generate are part of the same history.
Perpetual fills are journaled under the base asset with direction LONG or SHORT.

How your Bitget key is stored

Keys are handed to the server once over HTTPS and written to Supabase Vault, which encrypts secrets at rest. They are decrypted on the server only for the duration of an import, are never returned to the browser, and are deleted from the vault when you remove the connection. The connect form will not accept a key until you confirm it is read-only.

What gets imported from Bitget

The importer reads fills and writes closed trades. Here is exactly what ends up in the journal.

Fills become closed trades

Exchanges report individual fills; the journal records trades. Fills are walked in time order per symbol using average cost, and one closed trade is written each time your exposure returns to flat - so a position you scaled into over five orders is one trade, not five rows.

Entry, exit, quantity and direction

Each trade gets its average entry price, average exit price, quantity and a LONG or SHORT direction, so shorts on perpetuals are recorded correctly.

Fees and net P&L

Fee costs reported with each fill are summed into the trade's trading fee, and both gross and net P&L are stored along with the P&L percentage on the entry value.

Open and close timestamps

The first fill's time becomes the open time and the last fill's time becomes the exit time, which is what drives hold-time stats and the daily profit calendar.

No duplicates on re-import

Every imported trade carries an id derived from its exchange fill ids. Importing again skips trades that already exist, so you can sync as often as you like.

Positions still open are left alone

Anything not yet closed on the exchange is reported in the import summary but not written to the journal until it closes. Balances, deposits and withdrawals are never read.

Or import a Bitget CSV

For history older than the API returns, for markets the connection does not cover, or if you would rather not create an API key at all.

1Download a trade or order history export from the exchange.
2Upload it in the journal's CSV import. The mapper reads the header row and suggests which column is the symbol, open and exit time, entry and exit price, quantity, direction and fees.
3Map any symbols the journal does not recognise to an asset from the list, or leave them out.
4Import. The same de-duplication as the exchange sync applies, so the CSV and API paths can be mixed on one ledger.

What the journal does with your Bitget trades

Once the trades are in, the stats are computed for you - the same analytics whether trades were imported or typed in.

Win rate and profit factor

Win rate, profit factor, average profit per trade, biggest winner, biggest loser, total fees and average hold time - computed from the imported trades, not typed in.

Daily profit calendar

A calendar of green and red days so you can see whether losses cluster on certain days or after certain sessions.

Monthly reports

Net profit, trade count, win rate and profit factor summarised per month, so you can measure improvement over time rather than trade by trade.

Review every trade

Every imported trade sits in your history with entry, exit, fees and P&L, and you can add notes, a setup and an execution type after the fact.

The journal is free for up to 10 manually entered trades a month, with the same stats, calendar and reports. Exchange sync and CSV import are Pro features at $19/mo or $149/yr, and every new account starts with 30 days of Pro. See full pricing.

Bitget trade journal FAQ

Does Trnd Tools need trading permission on my Bitget API key?

No. The only call Trnd Tools makes is to your Bitget trade-history endpoint. Create the key with read-only permission and leave trading and withdrawals disabled - the connect form will not accept a key until you confirm it cannot withdraw funds, and nothing in the import needs more than read access.

Why does the Bitget connect form ask for a passphrase?

Bitget signs every API request with a passphrase you set when the key is created, in addition to the key and secret. Without it Bitget rejects the request. The passphrase is stored server-side with the other credentials and is never returned to the browser.

How far back does the import go?

The first sync pulls your full available history (up to 12 months on most venues; Binance returns everything it has). After that a background job checks every hour and only fetches fills that are newer than the last one it saw, so you never re-import anything. Exchanges that limit API history (OKX and MEXC keep 30-90 days) can be topped up with a CSV export.

Is the Bitget sync included in the free plan?

No. The free plan is manual entry for up to 10 trades a month with the same stats, calendar and reports. Exchange sync and CSV import are Pro features ($19/mo or $149/yr). Every new account gets 30 days of Pro on signup, so you can connect Bitget and import before deciding.

Stop tracking Bitget trades by hand

Create a free account, connect Bitget during your 30 days of Pro, and see your real win rate and profit factor from the trades you have already made. Free for up to 10 trades a month after that.