Link Your External OKX Exchange Account

Modified on Thu, 12 Nov at 4:05 PM

Link Your External OKX Exchange Account

This guide covers how to create an API keys on the OKX exchange to Link your account to BitGo.


Before you start

  • Region availability (as of July 2026): Link currently supports OKX in the US region only with Other regions are coming soon.

  • Make sure you're on your main OKX account.

  • You'll create the API key in OKX's API Management page, then enter the credentials into BitGo.


1. Create the API key on OKX

In API Management, click Create API Key and configure it as follows:


Passphrase: choose your own.

The passphrase is required to view API info and access its interface. OKX cannot recover a lost passphrase — you'll need to create a new API key if you lose it.


IP Address Allowlist (optional) — allowlist these addresses:

  • 54.201.131.213/32
  • 52.39.41.139/32
  • 52.43.255.93/32
  • 35.164.184.184/32
  • 54.214.57.139/32
  • 18.220.107.76/32
  • 18.222.87.170/32
  • 3.137.109.219/32
  • 18.156.154.77/32
  • 52.59.4.20/32


Permissions: Read access is sufficient to connect your account and view balances and positions. To enable transfers and withdrawals through BitGo, you will also need write permission. For intra-account transfers (e.g. between Funding and Trading), the key needs a Trading permission as well.


Click Submit and complete the security verification. OKX will then display your Key and Secret.


2. Link your account on BitGo

  1. Navigate to the Portfolio tab in BitGo and click + Link Account in the top-right corner.

  2. Select OKX.

  3. Enter your Key under API Key and your Secret under API Secret, then click Connect Account.





Back to list of exchanges




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article