Wallet and TradingView

Sign-in wallet and account boundary

The sign-in signature verifies the account wallet. It determines the account and the available bot list. After sign-out or sign-in with another wallet, the previous wallet’s selected bot, connection and local drafts do not carry over. A trading wallet is connected separately to a specific bot and may use the same address, but it has a different role.

Wallet

Select the bot → Connection → Wallet → Connect bot wallet. Approve access in your wallet and refresh status. Each bot has its own binding, even when using the same address.

TradingView

In Connection → TradingView, copy the URL and message template into the TradingView alert. Use the selected bot template; update the alert after changing its binding. Check delivery in Signals.

Approval errors

Read the exchange rejection reason. If the API access limit is reached, review unused exchange approvals. Do not revoke a running bot’s access. A saved binding does not confirm that permission is still valid.

API access names

New API access names include the bot type: SPOT, PERPS, GRID SP or GRID PP, followed by an identifier. Names are limited to 16 characters. Existing authorizations are not renamed automatically. When removing an old authorization, compare its API agent address with the selected bot’s connection details.