Starting from version 7.2, the Tiger.com terminal has added support for the decentralized exchange AsterDEX with full trading functionality on the spot and futures markets.
To set up the connection, follow these steps:
1
Logging in to the Exchange Website
Go to the AsterDEX exchange website and open the More -> API Management section:
2
Connecting a Wallet
In the top right corner, click the Connect Wallet button and choose one of the available wallet connection methods (log in with email, WalletConnect, or Binance Wallet):
3
Creating an API Key
Click the Create API button, enter an arbitrary name for the key, and confirm its creation:
4
Configuring Trading Permissions
Activate the necessary permissions for trading ("Enable Futures" and "Enable Spot Trading"):
If necessary, you can restrict access by configuring a whitelist of IP addresses. Please note: in most cases, the IP address provided by your ISP is dynamic (it changes from time to time), and to continue trading, you will also need to update it in the API key settings.
5
Copying Keys and Saving Settings
Copy the public and secret API keys, saving them in a secure place, then click the Save button to apply the set permissions.
6
Adding a new connection in the terminal
In the Tiger.com terminal, go to the File -> Connections -> Setup section, click the + New Connection button, and select AsterDEX from the list:
7
Configuring and Activating the Connector
Enter the public and secret API keys saved earlier into the corresponding fields and click the Connect to AsterDEX button:
Upon successful setup, you will see a corresponding confirmation message and a green icon next to the exchange name in the connections list:
Troubleshooting
Error "Disabling hedge mode failed. Invalid API-key, IP, or permissions for action"
1. Required permissions are missing in the API key settings.
2. An IP address restriction is configured in the API settings, and the current device's IP address is not on the list.
3. Permission settings were not applied (the "Save" button in step 5 was not clicked).
4. API keys were entered incorrectly (an extra character or the API Public / API Secret fields are swapped).
1. Edit permissions for the existing API keys or create new API keys with the required permissions, then click the Save button to apply the settings (following steps 4 and 5).
2. Ensure the API keys are entered correctly.
