Skip to main content

Exchange API Account

How Exchange API accounts work, including API key and OAuth connections.

Written by Scott
Updated over a week ago

Adding Your Transactions: Overview → Exchange API → WalletExchange StatementCustom

An Exchange API Account allows you to create a direct connection to your exchange, automatically importing and syncing your transactions. This means you can see all trades and transactions in real-time and the impact they have on your portfolio and tax position.

There are two ways to connect, depending on your exchange:

1. API Key Connection

Most exchanges use this method. You generate read-only API keys within your exchange account and enter them into Recap to establish a direct connection.

Exchanges that support API key connection include Binance, Kraken, Bitfinex, Bitstamp, KuCoin, Gemini, and more.

2. OAuth Connection

Some exchanges support a simpler sign-in method. Click "Sign in with Exchange" when prompted in Recap, and you'll be redirected to your exchange's login page to authorise Recap. No API keys needed.

Exchanges that support OAuth include Coinbase and Uphold.

For step-by-step guides on connecting specific exchanges, see our API Supported Exchanges guides. You can also view the full list of supported exchanges on our integrations page.

Is it secure?

Yes — API connections in Recap are designed with security at every step:

  • We only ever ask for read-only API keys — Recap cannot make trades or withdrawals on your behalf.

  • We use a secure proxy to sync your account and we don't store or track unencrypted data.

  • Once retrieved, your data is encrypted with your personal secret phrase. Only you can decrypt and view your account — not even Recap can see it.

Learn more on our Security page.

What if my exchange isn't supported?

If your exchange doesn't support API or OAuth connections, you can import your transactions using an Exchange Statement Account (CSV upload) or a Custom Account. You can also drop us a line in support and we'll make sure it's on our backlog.

Did this answer your question?