Binance trading journal

FOQUS keeps a trading journal for your Binance futures account by itself. Every USDⓈ-M position goes in without manual entry, with its fees, funding and stop history. It needs an API key with one box ticked, Enable Reading, and it refuses a key that can trade. The journal is free forever.

What FOQUS records from Binance

FOQUS reads your USDⓈ-M futures account: perpetual contracts settled in USDT and USDC, such as BTCUSDT and BTCUSDC. A position appears in the journal the moment it opens. Its profit, stop and time in the trade update live.

WhatHow it shows in FOQUS
Fillsevery buy and sell: price, size, fee
Stop-loss and take-profitset, removed, triggered; a move shows as a removal and a new level
Fundingevery payment received or paid while the position is open
Liquidationa separate event on the trade's timeline
Limit entry ordersplaced, amended, cancelled
Account before entrybalance, equity and your other positions when you opened
Market snapshotprice change and volume over 5 minutes, 1 hour and 24 hours, RSI, funding, open interest
Order-book recordinga minute either side of every entry, add, partial close and exit, from Binance's own book

Here is what that looks like on a real trade from my public journal. A MARSCOINUSDT long at 4× leverage: entry on 4 September 2026 at 21:34:08 UTC, an add at 21:56:34, exit at the stop on 5 September at 00:36:45 UTC. The entry, the add and the exit were three orders, with fees of 37.60, 10.81 and 46.73 USDT, 95.14 USDT in all. Funding over the trade came to −47.64 USDT. The result on price was −3,375.07 USDT, and −3,517.85 USDT after fees and funding. I typed none of it.

FOQUS trade page: a MARSCOIN/USDT long on Binance at 4× leverage, result −3,518 USDT; realized −3,375, fees −95.14, funding −47.64, max drawdown −3,518, max profit +7,531; entry, stop and exit on the chart
A trade from the author's public journal on Binance USDⓈ-M, 4–5 September 2026. The app is shown in Russian (it also speaks English); times on the screenshot are UTC+2, in the text UTC.

The max drawdown and max profit on the screenshot are the trade's MAE and MFE: its largest paper loss and largest paper profit while it was open. How to check your stop and exit against them is shown on this same trade in the guide to MAE and MFE.

When you pay a fee in BNB, FOQUS converts it to USDT itself. It takes Binance's BNBUSDT price for the last closed minute before the fill, so that fee counts in the trade's result too.

The free plan includes 10 order-book recordings a day. Each holds the futures book, with the spot book of the same coin beside it if the coin trades on spot.

How to create a read-only Binance API key

Binance issues keys to accounts with two-factor authentication on and identity verification done. You also need to have deposited into your Spot Wallet at least once, any amount.

  1. On the Binance website, click the profile icon → Account → API Management → Create API. In the app, switch to Binance Pro: More → the Other section → API Management.
  2. Choose System generated. A Self-generated key (Ed25519 or RSA) won't do: FOQUS signs its requests with a system key's secret.
  3. Name the key, FOQUS for example, and confirm with 2FA or a passkey.
  4. Copy the API Key and the Secret Key. Binance shows the secret once and hides it after that.
  5. Check the key's permissions. Only Enable Reading should be ticked. Leave trading, withdrawals and transfers off.
  6. Don't add an IP access restriction. FOQUS publishes no list of its addresses and reaches Binance from several of them. Binance itself gives a system key without an IP restriction no permission but Enable Reading: that rule has applied since 30 January 2023.
  7. Create a FOQUS account and pick Binance under Connect your own account. Paste the key and the secret and click Connect exchange.

The names above are from Binance's English site. In other languages and in the app the labels may differ. For read-only keys on all three exchanges, see the guide to the read-only API key.

How FOQUS checks a Binance key

First FOQUS asks Binance for the key's permissions, with the apiRestrictions request. The key passes only if reading is on and nine write permissions are off: withdrawals, two kinds of transfer, four kinds of trading (spot and margin, margin, futures, portfolio margin), options, and trading over FIX. Otherwise the key is not saved. Next FOQUS asks for the account's mode: a Portfolio Margin account is not supported yet (Binance serves its orders and history through another API), and its key is not saved either. Then FOQUS reads the account's BTC deposit address to recognise the account, and the positions already open before you connect: it leaves those out of the journal.

Binance key check in FOQUS: the apiRestrictions request, Enable Reading on, nine write permissions off, the account off Portfolio Margin, and the account not yet connected, each refusal with the connect screen's words
Each check in the order FOQUS's code runs it; on the right, the connect screen's words.
  • FOQUS only reads. With your key it requests fills, orders, positions, fees and funding. Besides reading, the key serves two more requests: opening and renewing the account's data stream. None of them is an order.
  • What is stored. The API key and the secret. The secret is encrypted.
  • How to disconnect. Delete the account in FOQUS, and its trades are deleted with it. Delete the key itself on Binance, under API Management.

What FOQUS doesn't see on Binance

  • Other products. Spot and margin, coin-margined COIN-M futures, quarterly contracts with an expiry, and options stay out of the journal.
  • History before you connect. It holds too little to review a trade: an account's history at Binance has no order book, and Binance stops returning a cancelled stop with no fill after 3 days. So FOQUS records each trade itself, from the minute you connect. A position opened earlier stays out, even if you close it afterwards.
  • Other exchanges under the Binance name. FOQUS talks only to binance.com hosts (api, fapi and fstream). A key from Binance.US or another separate Binance exchange won't work there.
  • Your reasons. The exchange doesn't know your setup, plan or mistake. You mark those with tags and notes. What to add to a trade is shown in How to Keep a Trading Journal.

The position size calculator sizes your next position to its stop. If you keep a journal by hand, take the trading journal template for Excel and Google Sheets. Bybit, OKX and MetaTrader 5 accounts connect too, each in its own way: Bybit, OKX, MetaTrader 5. Choosing between journals? See FOQUS vs TraderMake.Money.

Binance trading journal FAQ

Do I need Enable Futures for FOQUS to see my futures?

No. Enable Futures is permission to trade futures, not to view them. Your futures account can be read with Enable Reading alone, and FOQUS won't accept a key with Enable Futures on.

Will my old Binance history be imported?

No, by design: an old history holds too little to review a trade. It has no order book, and Binance stops returning a cancelled stop with no fill after 3 days. FOQUS records each trade itself from the minute you connect: the stops, the account and market snapshots, the order book around each fill. Your old trades stay in Binance's history.

What does “The key is not read-only” mean?

The key has something on besides Enable Reading. Open the key in API Management, untick the extra boxes and connect it again. If FOQUS says “The key has no read access”, turn Enable Reading on.

Why does FOQUS say “Binance rejected the key”?

Binance did not accept the key and secret pair. Check that you copied both in full and that the key hasn't been deleted. It has to be a system-generated key from binance.com: a Self-generated key or a Binance.US key won't work here.

Can I connect several Binance accounts?

Yes, each with its own key, with no limit on the number of accounts. The same account can't be connected twice: FOQUS recognises it under another key too and says “This exchange account is already connected”.

Sources

A trading journal for other exchanges and brokers