New: Bithumb Caution & Delisting Alerts

Last updated

Your Bithumb feed now carries two trade-actionable risk events alongside listings: caution_released (caution designation lifted, often a positive technical signal) and spot_delisting (final removal from spot). Both travel over the same WebSocket connection as listings, with the same real-time delivery from our Tokyo endpoint.

What we broadcast

We don't forward every Bithumb announcement. The feed is narrowed to three trade-actionable event types, all emitted on the same WebSocket connection:

"spot_listing"        // 원화 마켓 추가 — new KRW listing
"spot_delisting"      // 거래지원 종료 — final removal from spot
"caution_released"    // 유의 종목 지정 해제 — caution lifted (often a technical bounce)

caution_released is our event name for the moment Bithumb lifts a caution designation already placed on a token (거래유의종목 지정 해제) — the token had previously been flagged for review (concerns around liquidity, regulatory status, persistent volatility, etc.) and is now returning to normal trading status. spot_delisting is the inverse outcome: final removal from the spot market (거래지원 종료).

See the message reference for the full schema and example payloads.

Korea's caution-designation framework

Korean exchanges run an investor-protection regime that has no exact equivalent on global venues. Rather than jumping straight to a delisting, an exchange first flags a token as an "investment caution" item (거래유의종목 / 투자유의종목) — a formal review status triggered by concerns such as thin liquidity, regulatory uncertainty, weak disclosure, or persistent abnormal volatility. Much of this is coordinated across the major domestic exchanges through the Digital Asset eXchange Alliance (DAXA), the self-regulatory body that maintains a shared caution framework — so a risk flagged on one Korean exchange is frequently mirrored on the others.

From the caution state a token resolves one of two ways: Bithumb either lifts the designation (거래유의종목 지정 해제 → our caution_released) once the concerns clear, or ends trading support entirely (거래지원 종료 → our spot_delisting). The public lifecycle actually has more stages than the two we forward — a preliminary warning, the formal designation, possible extensions, then either release or delisting — but only the release and the delisting are directly trade-actionable, so those are the two we put on the feed. Bithumb publishes each step in its official notice center; Investopedia's delisting primer covers the general mechanics, and the glossary defines both event names.

Trading implications

Both events have a clear historical price-reaction direction: spot_delisting is bearish (final removal from the spot market) and caution_released is bullish (caution status lifted, the overhang of forced selling clears).

Disclaimer. CryptoListing.ws is a real-time data feed, not a financial advisor. The directions above are observations of historical behaviour — not guarantees, predictions, or recommendations. Markets are noisy, signals fail, and past behaviour does not determine future outcomes. You are solely responsible for any trading decisions you make on the basis of these events.

Why a caution release can bounce

While a token sits under caution, trading conditions tighten: uncertainty about whether it will survive review pushes risk-averse holders to derisk, and some traders avoid opening new positions in a name that might be removed. That builds a persistent overhang of latent and actual selling pressure. When Bithumb publishes the release, that overhang clears in a single step — the existential question is answered, precautionary sellers are done, and the token returns to normal trading status. Historically that combination has produced sharp upward moves in the minutes after a release notice, especially on the isolated KRW market where Korean retail liquidity concentrates. The delisting case is the mirror image: spot_delisting confirms the worst outcome and typically triggers an immediate exit rush.

Detection & API

Both event types are delivered over the same WebSocket connection as listings, delistings, and airdrops. A typical caution_released message looks like:

{
  "type": "announcement",
  "title": "신세틱스(SNX) 거래유의종목 지정 해제",
  "ticker": "SNX",
  "publisher": "bithumb",
  "listingType": "caution_released",
  "detectedTimestampUs": 1745971200834000,
  "dispatchTimestampUs": 1745971200842117,
  "abnormalDetectionLatency": false
}

And a spot_delisting message:

{
  "type": "announcement",
  "title": "고트세우스 막시무스(GOAT) 거래지원 종료",
  "ticker": "GOAT",
  "publisher": "bithumb",
  "listingType": "spot_delisting",
  "detectedTimestampUs": 1745971200834000,
  "dispatchTimestampUs": 1745971200842117,
  "abnormalDetectionLatency": false
}

One detail worth knowing: a single Bithumb announcement frequently pairs a release with a delisting. A title like "신세틱스(SNX) 거래유의종목 지정 해제 및 (BCD, WTC) 거래지원 종료" simultaneously releases one ticker (SNX) and delists two others (BCD, WTC). We split these into two distinct WebSocket events with separate listingType values and deterministic IDs, so your bot can route each side independently — no parsing logic on your end. Multi-ticker, single-category announcements (e.g. "(BCD, WTC) 거래지원 종료") keep the listings convention: one event with the tickers joined comma-separated in the ticker field.

Filtering is a one-liner:

def on_message(ws, msg):
    data = json.loads(msg)
    lt = data["listingType"]

    if lt == "caution_released":
        clear_risk(data["ticker"])
    elif lt == "spot_delisting":
        unwind(data["ticker"])

Korean exchange listing alpha in 2026

Bithumb and Upbit remain two of the most reactive venues in crypto because their KRW markets are walled off from global USDT liquidity by Korea's capital controls. That isolation is what produces the kimchi premium, and it is why a Korean listing, caution release, or delisting tends to move price faster and further than the same event elsewhere. A caution or delisting on Bithumb can ripple to the same token on Upbit and back, so watching both Korean order books together is often more informative than either alone.

On these thin, fast-moving KRW markets, delivery speed is decisive. A Telegram relay of the same notice typically lands 150–500 ms behind the source and a post on X can trail by 2–10 seconds — an eternity when a caution release is repricing a token that Korean retail is watching in real time. A direct WebSocket push carries the structured event, with the ticker already extracted from the Korean-language title, without that intermediate relay hop.

For the cross-exchange picture, see Bithumb vs Upbit: Listing Strategy and the parallel Upbit Caution & Delisting Alerts, which covers Upbit's version of the same caution lifecycle.

Get started

All event types are included in every plan, the free SpeedTrial key and FreeDelayed (full feed, +240 ms) included. Grab an API key on Telegram via @CLWfeed, then check the pricing page and developer docs to get connected. Bithumb events are dispatched from our Tokyo endpoint wss://cryptolisting.ws; filter with ?cex=bithumb to scope your subscription.

This article is for informational purposes only and is not financial advice. CryptoListing.ws is a technical data feed service — see Legal.

Related

Subscribe to Bithumb risk events

Caution releases and spot delistings on the same WebSocket connection as Bithumb listings. See our pricing & tiers — free SpeedTrial key available, plus FreeDelayed (full feed, +240 ms).

Get started on Telegram