KuCoin API

Name: KuCoin API
Brand: KuCoin API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey25 EndpointsREST

For Agents

Trade spot crypto on KuCoin - read market data, place and cancel orders, manage balances, deposits, withdrawals, and inner transfers - using API key plus HMAC signing and an encrypted passphrase.

Install Jentic One Beta

Connect the KuCoin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KuCoin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with KuCoin API.

Place market, limit, and stop spot orders, including bulk submissions, on KuCoin trading pairs

Cancel a single order by ID and list active stop orders for monitoring

Fetch tickers, 24-hour stats, level-2 order book snapshots, candle klines, and trade histories

GET STARTED

Start building with KuCoin API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for KuCoin API, keeping it validated and agent-ready. The KuCoin API exposes 25 endpoints for the KuCoin cryptocurrency exchange covering server time, symbols and tickers, order books, klines, currencies, account balances, spot order placement and cancellation, stop orders, fills, deposits, withdrawals, and inner-account transfers. Authentication uses three coupled headers - API key, HMAC signature, and an encrypted passphrase - which the spec models as separate apiKey schemes. The base path follows /api/v1 and /api/v2 prefixes, with v2 reserved for newer deposit-address and inner-transfer flows.

Use Cases

Patterns agents use KuCoin API for, with concrete tasks.

★ Algorithmic spot trading bot

A trading bot subscribes to ticker, klines, and order book endpoints to compute signals, then places and cancels orders via POST /api/v1/orders and DELETE /api/v1/orders/{orderId}. KuCoin requires the API key, HMAC-SHA256 signature, and encrypted passphrase on every private call, so the signing layer is the bulk of the integration work. Direct integration takes 1-2 weeks; a structured client cuts that to a few days.

Place a limit buy via POST /api/v1/orders with symbol 'BTC-USDT', side 'buy', type 'limit', size '0.01', price '60000' and confirm the orderId in the response.

Stop-loss and take-profit automation

A risk system places stop orders via POST /api/v1/stop-order to bracket spot positions, then watches GET /api/v1/stop-order to confirm activation status. Stop orders sit alongside live limit orders in the KuCoin engine, which lets the bot off-load conditional execution to the exchange rather than holding logic in the bot.

Place a stop-loss via POST /api/v1/stop-order for symbol 'ETH-USDT', side 'sell', type 'limit', stopPrice '2900' and price '2895'.

Funding and treasury automation

A treasury workflow uses GET /api/v1/deposits, GET /api/v1/withdrawals, GET /api/v2/deposit-addresses, POST /api/v1/withdrawals, and POST /api/v2/accounts/inner-transfer to move funds in and out of KuCoin and between sub-accounts. Withdrawals require whitelisted addresses configured inside the KuCoin UI, so the API surface assumes prior wallet setup.

Apply a withdrawal via POST /api/v1/withdrawals with currency 'USDT', address '<whitelisted>', amount '500' and chain 'TRC20', then poll GET /api/v1/withdrawals to confirm status.

Agent-driven trading workflows via Jentic

An agent searches Jentic for 'place a kucoin order' and receives POST /api/v1/orders with its full input schema. Jentic computes the API key, HMAC signature, and encrypted passphrase from your Jentic One instance at request time, so the agent supplies only business inputs - symbol, size, side - and receives a structured response.

Use the Jentic MCP tool kucoin_place_order to place a market buy on 'BTC-USDT' with funds '50' USDT and return the orderId.

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for kucoin api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/market/allTickers

Get all tickers

GET

/api/v1/market/candles

Get klines for a symbol

GET

/api/v1/accounts

List accounts and balances

POST

/api/v1/orders

Place a spot order

DELETE

/api/v1/orders/{orderId}

Cancel an order by ID

POST

/api/v1/stop-order

Place a stop order

POST

/api/v1/withdrawals

Apply a withdrawal

POST

/api/v2/accounts/inner-transfer

Inner transfer between accounts

GET

/api/v1/market/allTickers

Get all tickers

GET

/api/v1/market/candles

Get klines for a symbol

GET

/api/v1/accounts

List accounts and balances

POST

/api/v1/orders

Place a spot order

DELETE

/api/v1/orders/{orderId}

Cancel an order by ID

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your KuCoin key, secret, and passphrase are stored once, encrypted, by your own Jentic One instance, which computes the request signature at execution time. None of the three secrets enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'place a KuCoin order' or 'list KuCoin balances', and Jentic returns the matching v1 or v2 operation with its parameter schema, abstracting the three-header signing model so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using KuCoin API through Jentic.

Why is there no official OpenAPI spec for KuCoin API?

KuCoin does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KuCoin API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the KuCoin API use?

Private endpoints require three coupled headers - KC-API-KEY, KC-API-SIGN (HMAC-SHA256 of the request), and KC-API-PASSPHRASE (encrypted with the API secret). The spec models these as three apiKey schemes that all apply together. Jentic computes the signature inside your Jentic One instance so the secret and passphrase never enter the agent's context.

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

Yes. Use POST /api/v1/stop-order with stopPrice and price fields 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 enforces weighted rate limits per endpoint group, with public market data on a separate counter from private trading endpoints. Limits are tightened for accounts that hit penalty thresholds - refer to docs.kucoin.com 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 currency, from-account, to-account, and amount. Install with pip install jentic and Jentic injects the signed headers automatically.

Does the KuCoin API support futures and margin trading?

This spec covers the spot REST API surface. KuCoin Futures and margin endpoints sit on a separate API (futures.kucoin.com) and are not enumerated here - bring those in via a separate spec when needed.

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

Yes. 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. Your own rules govern which operations and stored credentials the agent can use, and the key, secret, and passphrase stay inside your instance rather than entering the agent's context.

KuCoin API

Connect the KuCoin API to your agent

Capabilities

Start building with KuCoin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs