SPOT Margin HF Migration Completion Announcement - March 4, 2026

03/06/2026, 11:09:01

Dear KuCoin API Users,

Note: To understand the background and migration plan for this change, please read KuCoin’s previously published announcement “KuCoin Margin API Upgrade Announcement”: https://www.kucoin.com/announcement/kucoin-margin-notice-250702

KuCoin Margin API high-frequency (HF) migration was fully completed at 07:00:00 on March 04, 2026 (UTC). All low-frequency (LF) accounts for SPOT Margin have been migrated to HF accounts. Effective immediately, please use the HF APIs (endpoints listed in the API documentation) for SPOT Margin trading and related operations.

Related Endpoint Updates

Key Notes

Preferred parameters: For SPOT Margin, please prioritize using non-V2 account type parameters: MARGIN, ISOLATED.
V2 parameters: MARGIN_V2, ISOLATED_V2 have the same meaning as non-V2 parameters, but will be gradually replaced by non-V2 parameters.
Note: Some endpoints/scenarios may still accept or return *_V2 values. Please keep compatibility and migrate to non-V2 parameters following the rules below.

Account Type	API Scope	Meaning
`MARGIN`	Classic API	HF Cross Margin
`ISOLATED`	Classic API / Pro API	HF Isolated Margin
`MARGIN_V2`	Classic API	Same meaning as `MARGIN` (will be gradually replaced by `MARGIN`)
`ISOLATED_V2`	Classic API / Pro API	Same meaning as `ISOLATED` (will be gradually replaced by `ISOLATED`)

(1) Parameter Updates - SPOT Margin HF

No.	API Endpoint	Parameter Mapping & Notes All refer to SPOT Margin HF accounts	User Impact & Required Action
1	Classic REST - Get Transfer Quotas	Preferred: `MARGIN` (HF Cross), `ISOLATED` (HF Isolated) V2: `MARGIN_V2`, `ISOLATED_V2` (same meaning; phased out gradually)	Queries for SPOT Margin LF accounts are no longer supported.
2	Classic REST - Flex Transfer	Preferred: `MARGIN`, `ISOLATED` V2: `MARGIN_V2`, `ISOLATED_V2` (same meaning; phased out gradually) Rule: When `type` is `INTERNAL`, non-V2 and V2 are equivalent. When `type` is not `INTERNAL`, `MARGIN_V2` and `ISOLATED_V2` are not supported—use `MARGIN` and `ISOLATED`.	Transfers between SPOT Margin LF and HF accounts are no longer supported.
3	Classic REST - Get Account - Cross Margin	Preferred: `MARGIN` (HF Cross) V2: `MARGIN_V2` (same meaning; phased out gradually)	Parameter semantics unified: `MARGIN` represents HF Cross Margin; `MARGIN_V2` will be phased out.
4	Classic REST - Get Account - Isolated Margin	Preferred: `ISOLATED` (HF Isolated) V2: `ISOLATED_V2` (same meaning; phased out gradually)	Parameter semantics unified: `ISOLATED` represents HF Isolated Margin; `ISOLATED_V2` will be phased out.
5	Classic REST - Get Account Ledgers - Margin_hf	Response field: `accountType` Current: `MARGIN_V2`, `ISOLATED_V2` Next: `MARGIN`, `ISOLATED` (will gradually replace the V2 values)	Response field update: `accountType` currently returns V2 enum values and will gradually migrate to non-V2 enum values.
6	Abandoned Endpoints - Inner Transfer	Preferred (lowercase required): `margin`, `isolated` V2 (lowercase required): `margin_v2`, `isolated_v2` (same meaning; phased out gradually)	Transfers between SPOT Margin LF and HF accounts are no longer supported.

(2) Disabled Endpoints - SPOT Margin LF

The following endpoints are SPOT Margin low-frequency (LF) endpoints and are no longer available. Please do not continue calling them.

No.	API Endpoint	Status	User Impact & Required Action
1	Abandoned Endpoints - Add Order - V1	Disabled (may return “insufficient balance” error)	SPOT Margin LF endpoint is no longer available.
2	Abandoned Endpoints - Add Order Test - V1	Disabled	SPOT Margin LF endpoint is no longer available.
3	Abandoned Endpoints - Get Account List - Isolated Margin - V1	Disabled	SPOT Margin LF endpoint is no longer available.
4	Abandoned Endpoints - Get Account Detail - Isolated Margin - V1	Disabled	SPOT Margin LF endpoint is no longer available.

For more API discussions or feedback, please join our official KuCoin API Telegram group: https://t.me/KuCoin_API, or email us at api@kucoin.com.

We apologize for any inconvenience this may cause. Thank you for your continued support of the KuCoin API.

KuCoin API Team