MOAHook relays your TradingView alerts to exchange APIs, so each user must create API keys directly inside the exchange account.
This guide follows the same order as the screenshots and explains why each permission, IP restriction, and key value matters.
Viewing on mobile
On each exchange detail page, you can switch between PC and mobile screenshots. Exchanges with mobile screenshots open the mobile flow first on small screens; exchanges without them use the PC flow.
API security settings
For exchanges that support IP restrictions, allow only this IP and never enable withdrawal permissions. For Korea Investment, match the key environment and HTS ID.
Restrict supported exchanges to 64.176.225.121. For Korea Investment, validate paper/real environment and HTS ID.
Keep asset-transfer permissions such as Withdraw, Transfer, and Sub-account Manage disabled.
Secret Keys are often shown only once, so register them in MOABOT right after issuance.
Create the key in the order shown below, then enter the values in MOABOT Dashboard > Settings > API. Even if the exchange screen changes slightly, look for API Management, API keys, or API and connections.
Values to enter in MOABOT
Recommended settings
Cautions
Capture View
This is the standard desktop-browser flow for opening the exchange API management screen and creating a key. The wider screen makes permissions and IP restrictions easier to verify.
Desktop opens the PC flow first. On small screens, mobile screenshots open first when available.
What to do on this screen
Open the top-right account menu and enter API and connections.
Checkpoints
Next step: Click Create API key
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
On API and connections, click Create API key to start creating a new API.
Checkpoints
Next step: Enter API trading, IP, permissions, and Passphrase
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
Select API trading, enter 64.176.225.121 in IP allowlist, and select only Read and Trade permissions.
Checkpoints
Next step: Complete passkey security check
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
After Submit all, complete device verification when Passkey security check appears.
Checkpoints
Next step: Retry passkey verification
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
If verification fails once, retry in the same window or prepare another verification method.
Checkpoints
Next step: Check the Passkeys screen
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
If passkey issues continue, check registered passkeys in Security center > Passkeys.
Checkpoints
Next step: Reset passkey if needed
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
Use Reset passkey or Rename/Remove to clean up usable passkeys, then return to API creation.
Checkpoints
Next step: Verify passkey with phone number
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
If OKX asks for phone verification, finish security confirmation through Verify with phone number.
Checkpoints
Next step: Confirm the created API
Swipe horizontally to inspect the desktop screenshot.
Open
What to do on this screen
When the new key appears in API and connections, register API Key, Secret Key, and Passphrase in MOABOT.
Checkpoints
Swipe horizontally to inspect the desktop screenshot.
Open
Next Step
Open Settings in the MOABOT dashboard, choose the API tab, then enter each exchange value such as API Key, Secret Key, Passphrase, or Korea Investment account and HTS values. Telegram verification may be required before saving.