KuCoin API

What authentication does the KuCoin API use?

KuCoin's own docs state that private REST requests must contain five headers: KC-API-KEY, KC-API-SIGN (the base64-encoded HMAC-SHA256 of timestamp + method + endpoint + body, computed with your API secret), KC-API-TIMESTAMP, KC-API-PASSPHRASE (itself HMAC-SHA256-encrypted with the API secret for v2 keys) and KC-API-KEY-VERSION. This specification models three of the five as apiKey schemes that apply together, and marks them required on 15 of its 25 operations; the remaining 10 market-data operations need no credential. Your key, secret, and passphrase are stored by your own Jentic One instance rather than in the agent's environment.

Can I place stop-loss orders with the KuCoin API?

Yes. Use POST /api/v1/stop-order with clientOid, symbol, side and stopPrice, adding price for a limit stop, to register a conditional order on the matching engine. Active stops appear in GET /api/v1/stop-order until they are triggered or cancelled.

What are the rate limits for the KuCoin API?

KuCoin restricts private endpoints per account user ID and per endpoint, and public endpoints per IP, so market data sits on a separate counter from trading. Its docs give a Cloudflare IP ceiling that all endpoints share, currently 500/10s, plus a stated limit on each private endpoint's own page, such as 45 times/3s for POST /api/v1/orders. Check the KuCoin API docs for current figures and design retries with exponential backoff.

How do I move funds between my KuCoin accounts through Jentic?

Search Jentic for 'kucoin inner transfer', load POST /api/v2/accounts/inner-transfer, and execute it with clientOid, currency, from, to, and amount, all of which the operation marks required. You install Jentic One once from github.com/jentic/jentic-one, and your KuCoin key, secret, and passphrase stay in that instance rather than in the agent's environment.

Does the KuCoin API support futures and margin trading?

This specification covers the spot REST surface only. KuCoin Futures is served from a separate host, api-futures.kucoin.com, so it is a different API and is not enumerated here. Margin trading is not on a separate host: margin order endpoints such as /api/v1/margin/order are served from the same base as spot, https://api.kucoin.com, but this specification does not include them. KuCoin publishes official OpenAPI documents for both futures and margin at https://github.com/Kucoin/kucoin-universal-sdk/tree/main/spec/rest/api, so bring those in from there when you need them.

Can I limit what my agent is allowed to do with the KuCoin API?

Yes, on two levels. Because you run Jentic One yourself, you decide exactly which KuCoin operations your agent may call, so you can grant read-only access to market data like GET /api/v1/market/allTickers and GET /api/v1/accounts while withholding everything else. Money-moving operations such as POST /api/v1/withdrawals and POST /api/v2/accounts/inner-transfer are not available to the agent unless you deliberately add them to that set. KuCoin also scopes the credential itself: its API key permissions are General (read-only queries), Spot, Margin, Futures and Transfer, and the Transfer permission that covers withdrawals and deposit addresses requires IP restriction to be enabled. Your key, secret, and passphrase stay inside your instance rather than entering the agent's context.