Before you start
- The intended OKX account and supported account site.
- API key, secret, and passphrase from the same key.
- A clear choice of live or demo environment.
1. Understand which passphrase the form needs
When creating an API key on OKX, you choose an API passphrase. External applications use that passphrase together with the key and secret to authenticate the connection. Entering your OKX sign-in password in its place will not make the credentials match.
OKX says a lost API passphrase cannot be recovered. If you no longer know it, create a replacement key through OKX, update the application connection, and revoke the old key when it is no longer needed. Do not send either passphrase to support or paste it into an AI conversation.
2. Create credentials for the correct account
Open API management in your OKX account, choose the intended main account or sub-account, and create a dedicated key. Name it so you can identify the Neron connection, choose a passphrase, and complete the security verification required by OKX.
Keep the key, secret, and passphrase together securely. All three must come from the same API key. A main account’s credentials are not interchangeable with a sub-account’s credentials, and a live key is not the same as a demo key.
3. Review Read and Trade permissions
Read permission covers supported account queries. Trade permission covers supported order placement and management. Withdrawal permission is not needed for this Neron trading connection. Review any additional permissions shown by OKX and enable only what your intended workflow requires.
If you use an IP allowlist, confirm the current addresses required by your supported connection. Do not enter your device’s address by assumption or invent a server address. Ask for the current connection instructions when the required allowlist is unclear.
4. Match the live or demo environment and account site
OKX issues credentials for live and demo environments separately. A connection error can occur when the key belongs to a different environment from the selected workflow. Confirm which environment the Neron feature is using before saving credentials.
OKX also uses different API domains for certain regional account sites. If your account is registered through a regional site, verify that the current Neron connection supports that site and market. Changing the passphrase will not fix an unsupported account-domain combination.
5. Save the three fields and inspect the connection check
In Neron’s bot API settings, enter the API key, API secret, and API Passphrase. The passphrase field is shown for OKX and Bitget. Save the connection and run the API check, then read each result and warning.
The current OKX readiness check can authenticate the connection and inspect supported read access without placing an order. It cannot prove Trade permission by sending no order, so a reminder to confirm Trade access may still appear. A working read check should not be interpreted as a completed live-trading test.
6. Troubleshoot authentication before enabling automation
For an invalid-passphrase response, check the API passphrase rather than the sign-in password. Verify that the key, secret, and passphrase belong together. For an environment error, compare live versus demo. For an IP error, review the supported allowlist. For a regional-domain error, check account-site support.
If a problem remains, share the error code, time, account site, and selected environment with support while removing credentials and personal account details. Do not repeatedly change permissions or resubmit live orders to test whether authentication has improved.
Official exchange references
Use the current documentation for your own account and region.