Connect Bybit with a read-only key
Flicker reads positions, balances and orders with this key. Where Bybit reports its permissions, Flicker refuses a key that can trade or withdraw, so create a read-only one.
On Bybit
Sign in to Bybit on the web, open your profile icon, then API.
Choose Create New Key and name it Flicker.
Give the key read-only access. Leave every trading, transfer and withdrawal permission off.
API key permissions
- ReadSee positions, balances and ordersOn
- TradePlace or cancel ordersOff
- WithdrawMove funds outOff
Illustration. Each exchange names these permissions in its own words. Restrict the key to Flicker's IP address, 18.153.160.58. It's recommended for security.
Confirm with your 2FA, then copy the key and its secret.
Paste it below. Where the exchange reports it, Flicker checks what the key can do before saving it.
No Bybit account yet? Create Bybit account
Create a free account to connect Bybit
The key is checked before anything is saved, and you can remove it at any time.
Free for up to 4 exchange accounts; every portfolio feature is included.
After you connect, Bybit may email or text you about a new API login: that's this key. Your first history can take a few minutes to load.
Bybit at a glance
- Connect with
- Key and secret
- Synced
- Positions, balances and order history
- Stops and targets
- Not read yet
- Setup
- 6 steps
- First sync
- Positions while you connect; history can take a few minutes
- After that
- On each visit and once a day
What you'll see after connecting
- Every open position with entry, mark and unrealized P&L, beside your other exchanges.
- Bybit doesn't share stops with Flicker yet, so its positions read “Not reported by this exchange” and the loss-at-stop total leaves them out.
- Flicker's read on each asset you hold: its verdict and how many factors agree.
- Closed trades as a record and a weekly review. R needs the stop at entry, which Bybit doesn't share yet.
If something goes wrong
When Bybit rejects a key, check that it was copied whole, has read access and allows 18.153.160.58. Each message below comes with its fix.
- Bybit rejected this key.
- Create a new read-only key on Bybit and paste it here.
- Bybit refused the request.
- Try again in a minute. If it repeats, create a new key.
- Couldn't reach Bybit.
- Try again in a minute.
- Too many key checks.
- Try again in an hour.