Verifying with Bybit
To verify a balance you hold on Bybit, you create a Read-Only API key on Bybit and paste it into Scrya. An API key is a pair of codes that lets an app look at your account without your password. No funds move.
What permission to choose
Choose Read-Only. Scrya only reads your wallet balance, so that’s all it needs.
Never choose Read-Write for Scrya, and never enable trade, withdrawal or transfer permissions. Scrya doesn’t need them. Keeping the key read-only is up to you, so check it before you paste it in.
Which balances Scrya counts
- Unified Trading Account only. Scrya reads the balance in your Bybit Unified Trading Account. It doesn’t see your Funding account.
- One account. Scrya reads only the account the key was created on, not your other sub-accounts.
If the asset is in your Funding account, you can transfer it to your Unified Trading Account inside Bybit before you connect. That’s a move between your own accounts, not a withdrawal. Otherwise Scrya records a lower balance, or zero.
Create the key on Bybit
Bybit only lets you create API keys on its website, not in the app.
- Sign in at bybit.com on the web.
- Click your profile icon (top right), then API.
- Click Create New Key, then choose System-generated API Keys.
- Keep API Transaction selected — do not choose Connect to Third-Party Applications. Scrya uses a personal API Transaction key.
- Give the key a name you’ll recognise, such as “Scrya read-only”.
- Under API Key Permissions, choose Read-Only.
- For IP access, choose No IP restriction.
- In the permissions list, tick the Assets / Wallet read access Scrya needs to see your Unified Trading balance.
- Click Submit and enter your two-factor code.
- Copy the API Key and API Secret. Bybit only shows the secret once. If you lose it, delete the key and create a new one.
Add the key in Scrya
- Open your verification request and click Start Verification next to the asset.
- Choose Centralised exchange, then Bybit.
- Paste Bybit’s API Key into API Key and its API Secret into API Secret.
- Click Connect exchange.
Scrya encrypts the key and secret before storing them, then checks your balance straight away. When the check succeeds you’ll see Verified and your Verified balance. Click Close.
Verified with Bybit before? Scrya may offer a saved key under Use a saved API key or add a new one. Choose it and click Reuse and verify.
Should I restrict the key to an IP address?
No. Choose No IP restriction. Scrya’s checks don’t come from one fixed address, so there’s nothing you could add. If the key only works from certain addresses, Bybit rejects Scrya’s check, and Scrya asks you to remove the restriction or create a new key without one.
Troubleshooting
- Invalid credentials: the key or secret looks too short or contains characters keys don’t use. Copy the full value again.
- Couldn’t connect to Bybit: Bybit refused the key. Check you copied both values in full, chose Read-Only with read access to your wallet, and chose No IP restriction. If the message mentions the time being out of sync, wait a moment and try again.
- Balance lower than expected: the asset is probably in your Funding account. See Which balances Scrya counts.
- Something went wrong on our side: this one’s on us. Note the reference (ERR-XXXX-XXXX) and see Error references.
More help: Troubleshooting.
Revoke the key
Once your verification shows Verified, you can delete the key. Go back to your profile, then API, find the key you named for Scrya and delete it.
After that, Scrya can’t reuse the key, so you’d create a new one for a future request. Scrya deletes its own encrypted copy 30 days after your verification completes. See Revoking your API key.
