Skip to content
Aegis Docs

API Key Rejected

Cause

Section titled “Cause”

An API key rejection means the exchange refused the request made by the Aegis bot. Common causes:

  • Wrong permissions — the key is missing Futures Trading or Derivatives Trading permission, or has spot-only permissions on a futures key
  • Wrong key type — HyperLiquid uses an agent wallet (generated private key), not a standard API key/secret pair; using the wrong format will result in authentication failure
  • Key revoked or expired — the key was deleted or deactivated on the exchange side
  • IP restriction mismatch — the key has IP whitelist enabled and the Aegis server IP is not in the allowlist

Remedy

Section titled “Remedy”
  1. Log in to your exchange account
  2. Check the API key status and permissions:
    • For Binance: verify Futures Trading is enabled and Withdraw is disabled
    • For HyperLiquid: verify the agent wallet address is correct and the agent is authorized on the main account
  3. Compare permissions against the matrix in API Keys Overview
  4. If the key is revoked or invalid, create a new one following the guide for your exchange:
  5. In Dashboard > Futures Wallets, remove the execution wallet with the rejected key
  6. Re-add the execution wallet with the new, valid API credentials