Connect KuCoin

HyperionX offers two KuCoin authentication methods:

• OAuth Login is the preferred linked-account method. Authorization occurs on KuCoin's website; users do not manually create or paste an API secret or passphrase. It requires a valid, active HyperionX cloud session on this Windows user.
• Manual Classic API fields are the direct fallback for an existing KuCoin API key, secret, and passphrase.

Both paths use KuCoin Classic Spot and Futures capabilities. They do not enable KuCoin Unified Trading Account routing in HyperionX.

Release certification is still required

KuCoin is Current in the connection picker, but public release certification is still required. OAuth can finish as read-only or trading-enabled according to the permissions KuCoin proves to HyperionX. Test the selected market and account with controlled size.

Check eligibility before connecting

KuCoin product availability and restrictions vary by country, account region, verification status, and product. Follow current local law and KuCoin's terms. Do not authorize, fund, or trade Spot or Futures if the activity is not permitted for you. Do not use location-masking tools to bypass a provider restriction.

Add The KuCoin Connection

1. Open Connections > Configure....
2. Select Kucoin under available connections, then select Add.
3. Select the new entry under Configured connections.
4. Set a recognizable Name.
5. Turn Load Spot and Load Futures on or off for the markets this connection should load.

Keep the connection selected and complete one authentication method below.

Method 1: OAuth Login

KuCoin describes its official Fast API Service as an OAuth 2.0 linked-account flow that does not require manual API-key or passphrase setup.

Before starting, validate the HyperionX license/cloud session in the desktop. OAuth linking and later gateway access exchange that authenticated HyperionX session for a short-lived KuCoin gateway token. If the HyperionX cloud session is missing, invalid, or close to expiring, the OAuth connection cannot be linked or used even when the public KuCoin website is reachable.

1. Confirm that the HyperionX cloud session is valid.
2. Select OAuth Login in the KuCoin panel.
3. HyperionX opens the authorization page in your browser. Verify that the address belongs to KuCoin before entering credentials.
4. Sign in to KuCoin using the normal account login and complete any security checks.
5. Review the requested account and permissions, then authorize only the capabilities you intend to use.
6. Return to HyperionX and wait for the OAuth status to update.
7. Confirm whether the result says private reads only or that approved Classic trading permissions are enabled.
8. Select OK, open Connections, and select the saved KuCoin connection.

If browser authorization is still pending, select OAuth Login again. HyperionX resumes the same unexpired server session where possible instead of creating a second link.

The desktop stores the linked connection identity, not a manually entered KuCoin API secret. Disconnecting from the OAuth button unlinks the HyperionX gateway connection only after the server confirms it. Also review authorized applications and API access in KuCoin when retiring a device or account link.

Method 2: Manual Classic API Key

Use this method only if you intentionally created a KuCoin Classic API key. The official KuCoin API introduction documents the Classic API and permissions.

Create The Key At KuCoin

1. Sign in to the official KuCoin website and open its current API Management page.
2. Create a dedicated key for HyperionX rather than reusing a key from another application.
3. Create and securely record the API Key, API Secret, and API Passphrase. KuCoin does not make all of these values recoverable later.
4. Record the API key version shown in API Management. New keys normally use version 3, but HyperionX must match the value shown for that key.
5. Grant General for required private reads.
6. Grant Spot only if HyperionX should place and cancel Spot orders.
7. Grant Futures only if HyperionX should place and cancel Futures orders.
8. Do not grant Withdrawal permission. HyperionX trading does not require it.
9. Use an IP allowlist when appropriate and when the desktop's public IP is stable. Update the allowlist before connecting from a changed IP.

KuCoin's current permission reference states that General is read-only, while Spot and Futures allow trading for their respective markets. Withdrawal is a separate permission and is not required by this integration.

Enter And Test The Key In HyperionX

1. In the selected KuCoin connection, expand Advanced API settings.
2. Expand Show manual API fields.
3. Enter API Key, API Secret, and API Passphrase.
4. Set API Key Version to the value shown by KuCoin.
5. Select Test Credentials.
6. Wait for confirmation that private account access works.
7. Select OK, open Connections, and select the saved KuCoin connection.

Selecting Test Credentials switches this connection to manual API-key authentication. Never paste these values into Rion, Code Lab, logs, screenshots, support messages, or source control.

Switch Authentication Methods Safely

Treat OAuth and Manual Classic API keys as separate credentials and use only one method per configured connection. Changing the active local mode does not prove that the other method was erased or revoked remotely.

Existing credentials can remain

Selecting Test Credentials changes the connection to Manual Classic API-key mode, but it does not remotely unlink an existing OAuth connection. Conversely, disconnecting OAuth returns the local connection to Manual API-key mode and does not clear manual API key, secret, or passphrase values that were already saved.

When moving from OAuth to manual credentials:

1. Use Disconnect KuCoin and wait for HyperionX to confirm that gateway unlinking completed.
2. If the OAuth-created KuCoin key should no longer exist, remove it in KuCoin API Management as a separate provider-side step.
3. Prefer a new configured connection for the manual key. If reusing the connection, verify every manual field before selecting Test Credentials.

When moving from manual credentials to OAuth:

1. Revoke the old manual key at KuCoin if it should no longer work.
2. Clear the saved manual fields, or create a separate connection rather than retaining two usable credential sets in one entry.
3. Validate the HyperionX cloud session, complete OAuth Login, and verify the resulting read/trade capabilities.

After either transition, close and reopen Connections > Configure... and verify the intended method and status before connecting. Also verify authorized applications and keys in KuCoin; the desktop status is not a substitute for provider-side revocation.

Verify The Account And Market

After connecting:

1. Confirm the intended Spot and/or Futures account appears.
2. Confirm the instrument belongs to the same market scope as the selected account.
3. Verify public market data independently from private account access.
4. Check Log for the validated OAuth capabilities or manual credential result.
5. Use LocalPaper for the first order workflow.

Spot permission does not grant Futures permission, and Futures permission does not grant Spot permission. A linked OAuth account can also be read-only even when market data works.

Troubleshooting

Symptom	Check
OAuth reports that a HyperionX session is required	Validate or sign in to the HyperionX cloud session, then retry OAuth. A KuCoin login alone is not sufficient.
OAuth browser does not finish	Complete all KuCoin browser prompts, return to HyperionX, then select OAuth Login again to resume an unexpired pending session.
OAuth says private reads only	Review the permissions authorized at KuCoin. HyperionX will not infer or elevate trading access.
The connection uses manual credentials after OAuth disconnect	OAuth disconnect returns the local entry to Manual API-key mode. Clear or revoke retained manual credentials if they must not become active.
Manual test says invalid passphrase	Use the API passphrase created with the key, not the KuCoin account password.
Manual test fails after recreating a key	Replace the key, secret, passphrase, and version as one set.
Spot works but Futures does not	Confirm Load Futures, Futures permission, account eligibility, and the instrument/account scope.
Works on one network but not another	Check the key's IP allowlist and the current public IP.

If an order outcome is unknown, stop new submissions and follow Connection Recovery.