How to get the OKX API Key? (Developer tools)

Accessing Developer Tools on OKX

1. Log in to your OKX account using verified credentials and two-factor authentication.

2. Navigate to the top-right corner of the dashboard and click on your profile icon.

3. Select Developer Tools from the dropdown menu to enter the API management interface.

4. Ensure your account has completed identity verification at Level 2 or higher before proceeding.

5. Confirm that no active security alerts or restrictions are applied to your account.

Creating a New API Key

1. Inside Developer Tools, locate and click the Create API Key button.

2. Choose the appropriate permission type: Read-only, Trade, or Withdrawal, based on operational needs.

3. Assign a custom name to the key for internal tracking—this name cannot be edited after creation.

4. Set IP address restrictions by entering one or more IPv4 addresses; leaving this field blank grants access from any IP.

5. Enter your current Google Authenticator code or hardware token value to authorize the request.

Securing and Storing Your Credentials

1. After confirmation, OKX displays the API Key, Secret Key, and Passphrase simultaneously only once.

2. Copy each field manually—browser auto-fill or password managers must not be used during this step.

3. Store all three values in an encrypted offline vault; never commit them to version control systems or cloud notes.

4. Immediately configure your trading bot or application with the credentials before closing the browser tab.

5. Verify functionality by initiating a test request to the /api/v5/account/balance endpoint using HMAC-SHA256 signature logic.

Managing Existing API Keys

1. Return to Developer Tools to view all active keys, including creation timestamp, permission level, and bound IP list.

2. Click the Edit icon next to a key to modify its name or IP restrictions—permissions and passphrase remain immutable.

3. Use the Disable toggle to suspend a key without deleting it; disabled keys retain their configuration history.

4. Initiate permanent deletion only after confirming zero active integrations depend on that specific credential set.

5. Monitor the Last Used timestamp column to identify stale or compromised keys requiring rotation.

Frequently Asked Questions

Q: Can I generate multiple API keys with different permissions under one OKX account?A: Yes. OKX allows up to 10 active API keys per account, each configurable with distinct permission scopes and IP whitelists.

Q: What happens if I lose my Secret Key or Passphrase?A: Neither can be recovered. You must disable the compromised key and generate a new one with identical settings.

Q: Does OKX support sub-account API key generation?A: Sub-accounts cannot independently create API keys. Only the master account may generate keys that operate across linked sub-accounts when enabled during creation.

Q: Is there a rate limit applied to API calls using my key?A: Yes. Public endpoints allow 10 requests per second; private endpoints are limited to 50 requests per second per API key.