Connect Deribit
Read-only. The journal never trades.
Deribit
hmac key
Could not connect
This venue is not ready to connect yet, so the form is disabled rather than taking a key it cannot use. Nothing has been stored. Your api secret has been cleared and must be entered again — we do not send a secret back to your browser.
⚠ This stores a secret
It is encrypted before it reaches the database and never
appears in a response or a log. It is still worth knowing: issue a key with trading and withdrawal disabled, and revoke it at the venue if you ever stop using this.
The credential is checked against the venue before it is
stored. If it turns out to allow trading or withdrawal, the connection is
refused and nothing is saved.
How to create the key
checked September 2026
Account → API → Add new key
- 1Sign in to Deribit and open Account → API.
- 2Add a new key.
- 3Set every scope to read. Deribit lets you choose the level per scope — account:read, trade:read, wallet:read.
- 4Save and copy the client ID and client secret.
Turn on
account:readtrade:readwallet:read
Leave off
trade:read_writewallet:read_writeblock_trade
Worth knowing about Deribit
- Deribit scopes are written as name:level. Anything ending in read_write is not read-only, whatever the name in front of it.
- Test-net keys will not work against the live site.
- You can delete this key at the exchange at any time. Doing so stops imports immediately and affects nothing else.
Exchanges move these settings without warning. If
what you see does not match, Deribit API settings ↗ is the
authority — and nothing here ever asks you to enable trading or
withdrawal.
What this connection can supply
crypto exchange
executions✓
open positions✓
fees✓
funding✓
Limits worth knowing
- Funding applies to perpetuals only.
- no balance history — the chart stays cumulative realized P&L, not an equity curve
- no stop-amendment history — the moved-stops pattern shows as unavailable