> For the complete documentation index, see [llms.txt](https://docs.ispecalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ispecalgo.com/en/isa-terminal/birzhi-i-podklyucheniya/chastye-oshibki-api.md).

# API errors

Use this page when an exchange connection cannot be created or reports an error.

## Quick check

* API Key and Secret are copied in full, without extra spaces.
* The exchange and market (Spot/Futures) are correct.
* Demo mode is enabled only for demo keys.
* The key has read and trading permissions.
* Windows time is synchronized.
* Futures position mode is checked: One-Way or Hedge Mode.

For Hyperliquid, check the trading account address and API wallet key instead of an API Key and Secret. Only One-Way is supported.

## Hyperliquid connection errors

* **No balance:** check the trading account address and network. Do not use the API wallet address as the account address.
* **Terminal fee not approved:** approve it in connection settings, sign with the main wallet, then click **Check**.
* **API wallet expired, removed or not approved:** create and approve a new API wallet on the exchange, then replace its private key in connection settings.

See [Hyperliquid](/en/isa-terminal/birzhi-i-podklyucheniya/hyperliquid.md) for the full guide.

## Invalid API key

The key was copied incorrectly or does not match the exchange or mode. Copy it again, check the exchange and live/demo mode, then create a new key if necessary.

## Invalid signature

Usually the Secret was copied incorrectly or does not belong to this API Key. Check both values; do not reuse an old Secret from another key. If unsure, create a new API Key + Secret pair.

## Permission denied

The key lacks required permissions. Enable account data reading and trading, save on the exchange and recreate the ISA Terminal connection if needed. Do not enable withdrawals.

## Timestamp / time error

Exchanges can reject requests when Windows time is incorrect. See [Time synchronization](/en/isa-terminal/baza-znanii/sinkhronizaciya-vremeni.md).

## Position mode error

Changing mode on the exchange website while a bot is running may cause rejected orders and stop the bot with a mode-change reason. Read the error and check connection mode. See [Position modes](/en/isa-terminal/birzhi-i-podklyucheniya/one-way-rezhim.md).

## Error after enabling a connection

If the connection saves but fails after enabling, read the terminal logs and error text. Check balance, key permissions and internet access. If it repeats, send the log to support using a [bug report](/en/isa-terminal/baza-znanii/kak-otpravit-bag-report.md).