Permission validation
PnLFlow rejects keys that can trade or withdraw and accepts read-only access.
OKX integration
An OKX journal for reviewing trades and trading habits
Synchronize history using an API Key, Secret and Passphrase without trading permissions, then review completed trades in one analytics workspace.
Read-only APIPnL · Win Rate · Profit FactorAuto sync
PnLFlow
What you get
Assembled trades
Executions are assembled into clear positions with entry, exit, duration and outcome.
Period statistics
Switch time periods and review PnL, trading quality and strategy results.
How it works
How to configure an OKX read-only API
How to configure an OKX read-only API
Create a dedicated OKX API key and save the API Key, Secret and your Passphrase. Leave only read permissions. If Trade or Withdraw is enabled, PnLFlow displays a clear error and does not save the connection.
After connection, synchronization imports available execution history and open positions. Secret values are not returned to the browser.
How to use OKX data
Separate outcome analysis from decision quality. A profitable trade can violate the plan, while a controlled loss can be correct system execution. Notes and scores in PnLFlow keep this context next to the numbers.
FAQ
Frequently asked questions
Why is the OKX Passphrase required?+
It is part of the API credentials created with the key in OKX. It is not your account password.
Can I enable trading permissions?+
No. A trading journal does not need them. PnLFlow intentionally rejects such connections.
Start reviewing your trades with real context
Create a free account and build your first report from actual trade history.