How to Get an OKEx API Key: A Step-by-Step Guide

·

Introduction

API keys are essential for traders and developers integrating OKEx's trading functionalities into third-party platforms like Biquant. This guide walks you through the secure process of obtaining your OKEx API key.


Step 1: Log In to Your OKEx Account

  1. Visit the OKEx official website using a desktop computer (mobile may limit functionality).
  2. Hover over your phone number/username at the top-right corner.
  3. Select "Personal Center" from the dropdown menu.

👉 Why use OKEx for trading?


Step 2: Navigate to API Settings

  1. In the Personal Center, locate "Trading Settings."
  2. Click "My API" to access the API management section.

Step 3: Create a New API Key

  1. Click "Create New API" (top-right of the page).
  2. Fill in the required details:

    • Remark Name: A descriptive label (e.g., "Biquant Integration").
    • Permissions: Check "Trade" for trading capabilities.
    • Security Verification: Enter SMS and Google Authenticator codes.

Step 4: Secure Your API Credentials

  1. After creation, return to "My API" and click "View" under Operations.
  2. Complete SMS/Google verification to reveal:

    • apiKey: Public identifier for your account.
    • secretKey: Private key (keep this confidential!).

⚠️ Never share your secretKey—it grants full access to your funds.


Step 5: Integrate with Third-Party Platforms

Copy the apiKey and secretKey into platforms like Biquant to enable automated trading.

👉 Maximize profits with OKEx API


FAQs

Q1: Is the OKEx API free to use?

Yes, OKEx provides API access at no cost, but standard trading fees apply.

Q2: What permissions should I enable for basic trading?

Select "Trade" only unless you need advanced features like withdrawals.

Q3: How often do API keys expire?

OKEx keys remain valid indefinitely unless manually revoked.

Q4: Can I restrict API access by IP?

Yes—OKEx allows IP whitelisting for enhanced security.


Best Practices

For advanced strategies, explore OKEx’s developer documentation.