TrueHold

HelpConnecting

Connect an exchange with a read-only API key

Create a read-only key on the exchange, paste it into TrueHold, and balances, positions and history appear. The key is validated before it is stored.

TrueHold reads exchange accounts through API keys that can only read. Trading and withdrawal permissions are never required, and a key that has them is not used any differently: the product only ever calls read endpoints.

Steps

  1. 01On the exchange, open the API management page and create a new key with read permission only. The exact permission name differs by venue; the coverage page for each exchange on this site shows which box to tick.
  2. 02If the exchange offers an IP allowlist, you can leave it empty for now or ask support for the addresses to bind. Read-only keys keep working without an allowlist on every exchange TrueHold connects.
  3. 03In TrueHold, open Exchanges and choose Link an exchange. Pick the venue, paste the API key and secret, and the passphrase where the exchange uses one.
  4. 04The key is validated against the exchange before it is stored. If validation fails, the exchange rejected the key or its permissions; check that read access is enabled and that the secret was copied in full.
  5. 05Balances refresh within seconds of a successful validation. Futures, margin and earn balances arrive with the same key as spot.

Which exchanges

Binance, OKX, Bybit and Backpack connect through their own APIs. Kraken, Coinbase, MEXC, Bitget, Gate, BingX and a long tail of other venues connect through a verified exchange library. If your venue issues API keys, try it; the coverage page lists the ones people ask about most.

Related

What TrueHold can and cannot do with your keys

Keys are read-only, validated before storing and encrypted at rest. They cannot trade or withdraw; revoking one on the exchange ends access at once.

Replace or rotate an API key

Open the exchange account in TrueHold, replace the key from its settings, and the account keeps its history. Expiring keys are flagged in advance.

Why a sync failed and what to do

A failed sync usually means a revoked or expired key or an exchange outage. TrueHold retries, emails you if it keeps failing, and lets you re-connect.

Still stuck?

Write to hello@truehold.xyz with the screen you are on. Answers become docs, so the next person finds it here.

Open TrueHold