Use this file to discover all available pages before exploring further.
The SpotClient trading methods cover four order systems on KuCoin’s spot exchange: High-Frequency (HF) Orders (the recommended, low-latency path), Standard Orders (the legacy REST interface), Stop Orders (trigger-based orders), and OCO Orders (One-Cancels-the-Other). All trading endpoints require authentication. For best performance and the lowest latency, use the HF endpoints — they operate on a dedicated matching engine and support synchronous result delivery.
Standard order endpoints (submitOrder, cancelOrderById, etc.) are deprecated. Prefer the equivalent HF order endpoints for all new development.
HF orders are processed on KuCoin’s high-frequency matching engine. Methods that end in Sync block until order matching completes and return the final order state synchronously.
submitHFOrder(params)
Places a limit or market HF order. Returns immediately with an orderId and optional clientOid; matching happens asynchronously.Endpoint:POST api/v1/hf/orders — 🔒 Auth required
Identical signature to submitHFOrder but the order never enters the matching engine. Use it to validate request signatures and parameter formatting.Endpoint:POST api/v1/hf/orders/test — 🔒 Auth required
Places an HF order and waits synchronously for matching to complete before returning the final order state.Endpoint:POST api/v1/hf/orders/sync — 🔒 Auth required
Array of up to 20 order request objects. Each object accepts the same fields as submitHFOrder.
submitHFMultipleOrdersSync(params)
Places up to 20 HF orders in a single request and waits synchronously for matching results before returning.Endpoint:POST api/v1/hf/orders/multi/sync — 🔒 Auth required
Array of up to 20 order request objects. Each object accepts the same fields as submitHFOrder.
cancelHFOrder(params)
Sends a cancellation request for an HF order by its orderId. This is asynchronous — the order may still be alive briefly after the call returns.Endpoint:DELETE api/v1/hf/orders/{orderId} — 🔒 Auth required
Sends an asynchronous cancellation request for an HF order using the client-assigned order ID.Endpoint:DELETE api/v1/hf/orders/client-order/{clientOid} — 🔒 Auth required
Cancels an HF order by clientOid and waits synchronously for cancellation confirmation.Endpoint:DELETE api/v1/hf/orders/sync/client-order/{clientOid} — 🔒 Auth required
Cancels a specified quantity of an HF order by orderId, rather than the entire order. Useful for partially cancelling large orders.Endpoint:DELETE api/v1/hf/orders/cancel/{orderId} — 🔒 Auth required
Returns all active (unfilled) HF orders for a symbol. Results are sorted by latest update time descending.Endpoint:GET api/v1/hf/orders/active — 🔒 Auth required
This method is deprecated as of 2025-03-13. Use getHFActiveOrdersPaginated() for new implementations.
getHFActiveOrdersPaginated(params)
Returns active (unfilled) HF orders for a symbol with pagination support. The returned data is sorted in descending order by order creation time.Endpoint:GET api/v1/hf/orders/active/page — 🔒 Auth required
Returns paginated completed (filled or cancelled) HF orders for a symbol. Sorted by latest update time descending.Endpoint:GET api/v1/hf/orders/done — 🔒 Auth required
Sets the Disconnection Protection (Dead Man’s Switch) for HF orders. After the specified timeout, all orders for the configured trading pairs will be automatically cancelled if this endpoint is not called again before the timeout expires.Endpoint:POST api/v1/hf/orders/dead-cancel-all — 🔒 Auth required
OCO (One-Cancels-the-Other) orders pair a limit order with a stop-limit order on the same symbol. When one leg triggers or fills, the other is automatically cancelled.
submitOCOOrder(params)
Places an OCO order on the spot market.Endpoint:POST api/v3/oco/order — 🔒 Auth required