CoinTools
KuCoin

KuCoin UTA-API Upgrade: WebSocket Disruptions Expected

KuCoin will upgrade its UTA-API on August 12, 2026, causing possible WebSocket disconnections and introducing API changes.

Published by: CoinTools
Direct answer

KuCoin announced a non-disruptive upgrade to its UTA-API scheduled for August 12, 2026, at 12:00 UTC, lasting up to 120 minutes. During this period, UTA WebSocket connections may experience temporary disconnections, data loss, or delays; users can reconnect to restore service. The upgrade introduces three API changes: a modification to the Get Trade History response for ADL fills, a new updateTime field in Get Position List, and new ipWhitelist requirements for sub-account API permissions. No user action is required unless they rely on the affected WebSocket or API features.

Announcement visual briefKuCoin
KuCoinAPI
Event at a glance
  1. 01

    Upgrade scheduled for August 12, 2026, at 12:00 UTC, expected to last 120 minutes.

  2. 02

    UTA WebSocket may experience temporary disconnections, data loss, or delays during the upgrade.

  3. 03

    Users can reconnect to the WebSocket to restore connection if issues occur.

Built from the official exchange announcement and verified facts in this article. Check the source page for final timing and scope.

Key facts

  • Upgrade scheduled for August 12, 2026, at 12:00 UTC, expected to last 120 minutes.
  • UTA WebSocket may experience temporary disconnections, data loss, or delays during the upgrade.
  • Users can reconnect to the WebSocket to restore connection if issues occur.
  • Get Trade History: when fillType is 'ADL', liquidityRole will be empty instead of MAKER.
  • Get Position List (UTA) adds response field updateTime for latest position update time.
  • Classic REST Add/Modify sub-account API: ipWhitelist required if permissions include Transfer (Withdraw).

Key timeline

Upgrade starts

Upgrade expected to end

Who may be affected

  • Users of KuCoin UTA-API WebSocket
  • Users of UTA REST Get Trade History
  • Users of UTA REST Get Position List
  • Users of Classic REST sub-account API with Transfer (Withdraw) permissions

Impact analysis

The upgrade is non-disruptive but may cause temporary WebSocket disconnections, data loss, or delays, affecting real-time data feeds for UTA users. API changes alter response fields: Get Trade History will return empty liquidityRole for ADL fills, Get Position List adds updateTime, and sub-account API now requires ipWhitelist for Transfer (Withdraw) permissions. These changes may require developers to update their code to handle the new fields and validation rules. No impact on trading functionality is mentioned beyond WebSocket connectivity.

What the announcement does not say

The announcement does not specify whether the WebSocket disruptions will affect all users or only some, nor does it detail the exact nature of data loss. It also does not clarify if the ipWhitelist requirement applies to existing sub-account API configurations or only new ones.

Risk notes

  • WebSocket disconnections may cause temporary loss of real-time data, but users can reconnect.
  • API response changes may break existing integrations if not updated.
  • Sub-account API changes may cause permission errors if ipWhitelist is not configured.
  • The upgrade is non-disruptive, but no guarantee of zero impact is provided.
  • This article is for verification of exchange official announcements only and does not constitute investment or trading advice.

This article is for information only and is not investment, legal, or tax advice. Digital assets are volatile and may result in loss of principal.

Frequently asked questions

Do I need to take any action before the upgrade?

The announcement does not require any pre-upgrade action. However, if you use the affected APIs, you may need to update your code to accommodate the changes after the upgrade.

What should I do if my WebSocket disconnects during the upgrade?

The announcement states that users may reconnect to the WebSocket to restore the connection.

Will the ipWhitelist requirement affect existing sub-account API configurations?

The announcement does not specify whether the requirement applies retroactively. It states that when permissions include Transfer (Withdraw), ipWhitelist is required.

Official sources

  1. Announcement of KuCoin API Upgrade (2026-08-12)| KuCoin

Collected material is used only for fact checking. If this page differs from the original announcement, the official page controls.