OKX mit deinem Trading-Bot verbinden

Why OKX

OKX runs one of the most active derivatives books outside the US and has invested heavily in unified margin and portfolio margin modes. The V5 API is consistent across spot, perps, futures, and options, which means a multi-product strategy can use one key.

Note: OKX is unavailable to US persons, and several other jurisdictions have specific restrictions; check OKX's terms before signing up.

Before you start

Complete OKX's KYC Level 1 (most countries) or Level 2 (full access) — basic API trading requires at least Level 1. Enable 2FA via Google Authenticator. Set a Fund Password — this is a second password OKX requires for sensitive account actions, including creating an API key.

Create the API key

1. Sign in and open Avatar (top-right) → API, or go to okx.com/account/my-api.
2. Click Create V5 API Key.
3. Enter a Name, e.g. noon-barbari.
4. Enter an API Passphrase — this is a third secret unique to OKX. It is NOT your account password and NOT your fund password; OKX uses it to derive a per-key signing token. Store it in your password manager.
5. Choose permissions (next section).
6. Complete 2FA + fund password + email verification. The Secret Key is shown once.

Set the right permissions

OKX uses two scopes plus a withdraw flag:

• ✅ Read — required, always.
• ✅ Trade — required for any strategy that places orders.
• ❌ Withdraw — leave OFF. Noon Barbari does not need it.

That is the entire surface — OKX folds spot, perp, futures, and options into the same Trade scope.

IP whitelist

Strongly recommended. On the create dialog, paste:

51.38.112.198

OKX allows up to 20 whitelisted IPs per key. If you also run scripts locally, add your home IP.

Important: when you set an IP whitelist, OKX puts the key into a 24-hour quarantine for trading — Read works immediately but Trade only activates after the cooldown. Plan around that.

51.38.112.198

Paste keys into Noon Barbari

OKX is the one venue where you need three values, not two: API Key, Secret Key, and API Passphrase. The dashboard has a dedicated field for the passphrase under Profile → Exchange keys. Once the API key is created, copy the public key and the secret into Noon Barbari from the Profile → Exchange keys section of your account. Keys are encrypted at rest with a per-user envelope key and only decrypted in memory while a strategy run is active — they never leave the worker that needs them.

If the exchange issues a third value (passphrase, API memo, sub-account label), there will be a dedicated field for it. Save the form and the dashboard will run a lightweight balance query to confirm the credentials work.

Test the connection

Noon Barbari will issue a single read-only balance request the moment you save the key. A green tick means the credentials authenticated and your permission scopes match what the strategy needs. A red error usually points to one of four things: wrong key/secret pair, missing permission, IP whitelist mismatch, or 2FA grace period not yet expired.

Once green, run a small paper trade for a day before flipping a strategy to live. Real execution exposes you to fees, partial fills, and slippage that paper mode cannot replicate.

Security tips

Treat exchange API keys like SSH keys to a production server — rotate them on a schedule and revoke them the moment you no longer need them.

1. Never grant withdraw — Noon Barbari only needs read + trade. A key without withdraw cannot move funds out of your account, no matter who steals it.
2. Use a sub-account if your exchange supports them — isolates the bot's capital from your spot stack and your manual trading.
3. Enable IP whitelist even when the exchange does not require it.
4. Rotate keys every 90 days — set a calendar reminder. The exchange's UI will let you create a new key and revoke the old one in the same session.
5. Enable exchange-side alerts for new API keys, failed logins, and large orders so you find out about a compromise within minutes, not days.

Häufige Fallen

• Forgetting that OKX needs a passphrase on every signed request — strategies that work on Binance/Bybit without the third value will fail until you provide it.
• Hitting the 24-hour Trade lockout after enabling IP whitelist and assuming the key is broken. It is not; wait it out.
• Confusing the Fund Password and the API Passphrase. They are different — the API passphrase is created when you create the key.
• Skipping Set Fund Password — OKX will block the key creation flow halfway through.

Fehlersuche

• 50111 — Invalid OK-ACCESS-KEY.

  Either the API Key string is wrong, or the key has not finished provisioning (OKX can take up to 60 seconds after creation). Wait one minute and retry.

• 50112 — Invalid OK-ACCESS-PASSPHRASE.

  The passphrase you typed into Noon Barbari does not match the one you set on OKX. There is no way to read the passphrase back from OKX — if you lost it, delete the key and create a new one.

• 50113 — Invalid Sign.

  The Secret Key is wrong, or your server clock is more than 30 seconds off. Noon Barbari syncs via NTP automatically; if you see this only when local-testing, check timedatectl status.

• Why does Read work but Trade always errors immediately after I set an IP whitelist?

  OKX enforces a 24-hour cooldown on the Trade scope after the first IP whitelist change. This is by design. Plan the rollover at least a day before you intend to go live.