Connecting Trading Accounts to TMM

Automatic imports currently cover 11 supported crypto exchanges. Coverage can include spot and futures activity, depending on the connected exchange and account type.

See the current list and setup instructions on the supported exchanges page.

TMM is built for read-only API keys and uses a key only to read trading data. On exchanges that report key permissions — including Binance, Bybit, OKX, Bitget, BingX and Kraken — a key that can place orders or withdraw funds is rejected during the connection permission check. Some exchanges do not expose a permission check; there, create the key with read-only access as the setup guide shows.

Whatever the key's permissions, TMM never places trades and never withdraws funds, and an accepted key is used only to retrieve the trading data the connected source makes available.

Not currently. Automatic imports are available for TMM's supported crypto exchanges. Stock, forex, options and traditional broker connections are not currently available.

Do not connect an unsupported account or upload credentials intended for another service.

Manual trade creation and CSV import are not currently supported. Trades enter the journal through supported automatic connections.

If you need manual or CSV import, check the product updates or contact support before choosing TMM for that workflow.

A rejected key almost always breaks one of four connection rules, so check them in order:

1. The key must be created with read-only permissions.

2. Do not reuse a key that you also use for trading.

3. Do not restrict the key to your own IP address — TMM connects to the exchange from its own servers, so an IP whitelist that lists only your address blocks the connection.

4. Configure the key exactly as shown on the my API keys page.

If the key still fails, open the support chat (the bubble in the bottom-right corner of the site, or Account & Settings - Help & Support - Support chat in the app) with the exact error text and support will check it.

Every exchange has its own API-key page, and TMM publishes a setup guide for each supported exchange on the supported exchanges page. Follow the guide for your exchange and create the key with read-only permissions.

Exchange documentation: Binance and Bybit.

Open the my API keys page, click the gear icon next to the connection and choose "Edit". This is what you use when the exchange revoked the old key and you created a replacement.

Editing works as long as the exchange account behind the key is the same one. If the key belongs to a different exchange account, add it as a new connection instead, so the imported history stays attached to the right account.

Yes. You can connect several API keys, including keys from different exchanges, and review the combined statistics in one place.

Filters across the site let you separate trades by API key whenever you want to review one account on its own. How many connections you can keep depends on your plan — the free plan allows one.

Yes. Freezing, on the API keys page, archives a connection: its trades stay in your journal as history, syncing stops, and the connection stops counting against your plan's API-key limit. It is meant for exchange accounts you have closed or will never trade on again. A frozen key also drops out of Top Traders and your public profile, and the free plan can hold up to three frozen keys.

Freezing is permanent on every plan except Pro, where you can request an unfreeze through support. The duplicate-key check also blocks adding a new key from the same exchange account, so on other plans the only way back is deleting the frozen key — which removes its history. Freeze a key only when you are sure you are done with that account.

Trades that are already imported stay in your TMM journal. They are removed only when you delete the API key inside TMM.

So if you are closing an old exchange account and want to keep its history, connect the key first, let the trades import, and then disable the connection.

Click the "Repair" button on the my API keys page — it reconnects the key and re-checks the exchange for missing trades.

If trades are still missing afterwards, contact support with the API key name and the date of the trade you expected to see.