Connect a KuCoin Classic account to KLINEO
The current KLINEO KuCoin connection supports KuCoin Classic production accounts, spot and USDT perpetual futures. It requires an API key, secret, API passphrase and the matching API key version. KuCoin sandbox connections and Unified Trading Accounts are not supported by this flow. Keep withdrawal and transfer permissions disabled.
Before you start
- An eligible KuCoin Classic account; confirm the account type before creating the key.
- A KLINEO account with Live access and an available connection slot.
- Funds in the KuCoin trading account for spot, or the corresponding futures account for futures. KLINEO does not require transfer permission.
Create and scope the KuCoin API key
- Open API Management from the official KuCoin account site. Create a separate key you can identify as your KLINEO connection.
- Save the API key, secret and API passphrase. The API passphrase is the value chosen for that key; it is not your login password or trading password.
- Enable General access for account verification and balances. Enable Spot or Futures only for the market you intend to use. Keep Withdrawal and Transfer disabled.
- Note the API key version attached to the key. Select the matching version in KLINEO rather than guessing when authentication fails.
Add the Live connection in KLINEO
Trading-account funding is performed at KuCoin. Do not enable transfer permissions simply because funds are in the wrong account. A balance visible elsewhere in KuCoin may not be available to the trading account selected for the order.
- Select Live in the workspace and open Settings → exchange connections → Connect exchange.
- Choose KuCoin. The Virtual/testnet connection option is disabled for this venue.
- Enter the API key, secret and API passphrase in the labeled fields. Choose API key version 2 or 3 to match the issued key; the current form defaults to version 3.
- Submit and wait for a successful connection test. If using perpetual futures, enable futures on the saved connection and complete its futures test.
- In the trading product, confirm KuCoin, spot or futures, the supported pair and the Live environment before continuing.
Respect the current account and market boundaries
KLINEO Virtual funds do not create a simulated KuCoin account. A successful account connection also does not establish that every workflow node or every KuCoin market is eligible for execution. Check the intended product’s connection and symbol checks.
| Area | Current boundary |
|---|---|
| Environment | Production only; no KuCoin sandbox connection. |
| Account API family | KuCoin Classic. Unified Trading Accounts use different APIs and are not covered. |
| Markets | Supported spot pairs and USDT perpetual futures, subject to product eligibility and permissions. |
| Credentials | API key, secret, API passphrase and matching key version. |
| Funding | Fund the matching KuCoin account yourself; keep transfer and withdrawal access disabled. |
Troubleshoot without expanding permissions
- Authentication error: recheck the exact API passphrase, copied secret and key version. Do not substitute the account’s trading password.
- Unsupported account or environment: confirm Classic and production. Do not switch to an unrelated environment to bypass account restrictions.
- Spot or futures unavailable: check the corresponding permission, futures enablement and successful futures test.
- No available balance: check the trading or futures account on KuCoin. Review exchange funding steps outside KLINEO.
- Rejected size or symbol: check the market’s current contract or spot order constraints. Another venue’s quantity rules are not interchangeable.
Revoke access and check existing exposure
- Review and stop the relevant bots or workflows, then inspect open orders and positions at KuCoin.
- Use Revoke in KLINEO Settings to remove the saved connection.
- Delete the API key in KuCoin API Management if it is no longer required or may have been exposed.
- Verify the final order and position state directly at KuCoin. Revocation prevents future authenticated access with that key; it does not close exposure.