Skip to content
ScryaHelp Centre

Verifying with Binance

To verify a balance you hold on Binance, you create a read-only API key on Binance 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

Leave Enable Reading as the key’s only permission. Scrya only reads your account balances, so that’s all it needs.

Never tick Enable Spot & Margin Trading, Enable Withdrawals or any other permission for Scrya. 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

  • Spot wallet only. Scrya counts the asset in your Binance Spot wallet, including any amount locked in open orders. It doesn’t see your Funding wallet, Earn, Futures or Margin.
  • One account. Scrya reads only the account the key was created on, not your other sub-accounts.
  • Binance.com only. Binance.US is a separate exchange, and its keys won’t work.

If the asset is in your Funding wallet, you can transfer it to Spot inside Binance before you connect. That’s a move between your own wallets, not a withdrawal. Otherwise Scrya records a lower balance, or zero.

Create the key on Binance

Before you start, Binance asks you to turn on two-factor authentication, verify your identity and make a deposit to your Spot wallet.

  1. Sign in at binance.com on the web — not the Binance app.
  2. Click the profile icon, then Account, then API Management.
  3. Click Create API.
  4. Choose System generated. A self-generated (Ed25519 or RSA) key won’t work with Scrya.
  5. Give the key a label you’ll recognise, such as “Scrya read-only”, and complete Binance’s security checks.
  6. Copy the API Key and Secret Key. Binance only shows the Secret Key once. If you lose it, delete the key and create a new one.
  7. Check the key’s restrictions. Only Enable Reading should be ticked, and IP access should be unrestricted. With no IP restriction, Binance only lets a system-generated key read, which is a useful safety net.

Add the key in Scrya

  1. Open your verification request and click Start Verification next to the asset.
  2. Choose Centralised exchange, then Binance.
  3. Paste Binance’s API Key into API Key and its Secret Key into API Secret.
  4. 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 Binance 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. Leave IP access unrestricted. Scrya’s checks don’t come from one fixed address, so there’s nothing you could add. A key restricted to certain addresses is rejected when Scrya checks your balance, and Scrya asks you to remove the restriction.

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 Binance: Binance refused the key. Check you copied both values in full, Enable Reading is on, the key isn’t IP-restricted, and you chose System generated.
  • Balance lower than expected: the asset is probably in Funding, Earn or another wallet Scrya doesn’t read. 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 API Management, find the key you labelled 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.