Create a dedicated key
Use a separate Binance API key only for Qantova. Do not share it with other bots, scripts or services.
Qantova
SECURITY CENTER
← Back to Qantova
Qantova is designed to operate with the minimum Binance API permissions needed for monitoring and Futures execution. Withdrawal access is not required.
Account and Futures data needed by the application.
Required only when you intentionally use Live execution.
Do not enable withdrawal permission for a Qantova API key.
Use a dedicated Binance API key for Qantova. Do not reuse a key that has broader account permissions.
Qantova includes separate Demo/Testnet and Live connection settings. Configure and understand your strategy, risk limits and runtime controls before connecting real funds.
Verify configuration and behavior without using real funds.
Switch only when permissions and risk settings are intentionally configured.
Use a separate Binance API key only for Qantova. Do not share it with other bots, scripts or services.
Enable only the permissions you actually need. More permissions mean more exposure if a key is ever compromised.
Binance recommends restricting API access to trusted IP addresses. If your network IP changes, update the Binance allowlist before using Live mode.
If you suspect that an API key or secret has been exposed, revoke it in Binance immediately and create a new dedicated key.
The public qantova.com website does not ask you to enter a Binance API key. Binance connection settings are configured from the desktop application's settings interface.
If you suspect unauthorized access, unexpected API activity or credential exposure, disable or delete the API key immediately from your Binance account.
Open Binance API Management ↗Qantova is trading software, not a custodian and not financial advice. Crypto Futures involve substantial risk. API restrictions reduce credential exposure but do not remove trading or market risk.