API security

API keys under your control.

Quantiva Trade routes execution to your account. You keep control of Binance, permissions, revocation, execution modes, and risk.

Base rules

Minimum API key requirements.

Restricted permissions

Use only the Binance API permissions required for your selected execution mode. Withdrawal permission is never required.

No exchange passwords

Quantiva Trade never asks for your Binance password, seed phrase, 2FA backup codes, or account recovery data.

Encrypted storage

When automation is enabled, API keys are stored encrypted to execute your configuration and can be removed from your account workspace.

Revocable by design

You can revoke Binance API keys directly in Binance at any time. Revocation immediately stops future exchange execution through that key.

Operational checklist

Configure, validate, and scale with mode separation.

Before connecting

  • Create a dedicated Binance API key for Quantiva Trade.
  • Disable withdrawals on the API key.
  • Confirm the selected market mode: Spot, Futures One-Way, or Futures Hedge.

During validation

  • Start with Demo or Paper before Binance Live.
  • Check that TradingView payload execution_mode matches the account profile mode.
  • Use a conservative position size while validating fills and logs.

If something looks wrong

  • Disable alerts in TradingView.
  • Switch the Quantiva Trade profile away from Binance Live.
  • Revoke the Binance API key and contact info@quantiva.trade.