Track3 Docs · OKX
Create a read-only OKX API key
Choose Read permission and keep the key, secret, and passphrase for Track3.
Before you start
Use the OKX website to create the key. You will choose a passphrase during creation, so prepare to keep it with the API key and Secret key. OKX cannot recover a lost passphrase; you must create a new key.
Create the key
- Sign in to OKX and open its API page.
- Follow the page's key-creation flow and choose a passphrase. We have not verified the exact button or field names on the website.
- Assign Read permission and review the key before using it in Track3.
Permissions: tick this, do not tick that
Tick: Read.
Do not tick: Trade or Withdraw.
Read covers account information, bills, and order history. Trade can place or cancel orders, move funds, and change settings; Withdraw grants withdrawal access. Track3 only needs Read.
IP restriction (optional)
OKX strongly recommends IP binding. You can bind up to 20 addresses to a key, including IPv4, IPv6, and network segments. OKX's docs describe the 14-day inactivity expiry only for unbound Trade or Withdraw keys.
Bind a stable public IP if that fits your setup. Home IPs can change, and a VPN or proxy changes the IP OKX sees. On iPhone and iPad, switching between Wi-Fi and cellular makes an IP allowlist impractical; a read-only key without IP binding is the practical mobile choice.
Copy the values
Keep the API key, Secret key, and the Passphrase you chose during creation. If you lose the passphrase, OKX cannot recover it; create a new key. Treat all three values as sensitive. We have not verified whether the Secret key is shown again after creation.
Enter them in Track3
These steps use the Track3 desktop app.
- Open Settings → Configuration → Exchanges → Add Exchange Configuration.
- Under Type, use Select CEX and choose OKX.
- Paste the API key into Api Key and the Secret key into Api Secret. Enter the OKX passphrase in Track3's Password field, then select Save changes.
Track3 labels the OKX passphrase field “Password.” The field labeled “Passphrase” is for another exchange.
Troubleshooting
- Clock skew: OKX rejects a request when the device clock is more than 30 seconds off (error 50102). Sync the device clock and try again.
- Wrong permission: Check that Read is enabled on the key. Track3 cannot currently check key permissions for you.
- IP not allowed: Check the bound addresses against the public IP OKX sees, especially after a home IP, VPN, or proxy change.
- Account type: We have not verified how unified or sub-account setups affect balances in Track3.
- Regional accounts: US, AU, and EU accounts are likely not supported; this has not been tested. They require regional API domains, while Track3 uses the global OKX domain.
Use the official OKX API documentation as the source of truth if the exchange screens change.