Bithumb Delisting Alert — caution & removal in real time

Bithumb is Korea's second major exchange, and its KRW-market decisions move the same retail-heavy flow that makes Upbit listings famous. A Bithumb delisting or an investment-caution designation can drain a token's book in minutes. CryptoListing.ws pushes both as structured JSON over WebSocket, the moment Bithumb publishes them.

Bithumb's caution-to-delisting path

Like Upbit, Bithumb rarely removes a coin without a preceding warning. A token is first placed under an investment-caution designation, kept there while Bithumb reviews it, and then either cleared or removed from the KRW market. Each transition is announced on Bithumb's official notice channel — and each is a potential trade.

The feed narrows this lifecycle to the two stages that actually drive trades: the delisting and the caution being lifted. Intermediate designations and risk-context deposit halts are detected but kept off the broadcast, so your handler only sees actionable events.

Two event types for Bithumb

Both share the same WebSocket as Bithumb's new-listing events, distinguished by listingType, so one connection covers Bithumb listings, delistings and caution releases together. For the listing side, see the Bithumb listing alert overview.

How Bithumb compares to Upbit

Both Korean exchanges run a multi-stage caution lifecycle and both drive fast, retail-led reactions — but they publish independently, on different notice boards, at different times. A coin under caution on one is not automatically flagged on the other. Trading either in isolation leaves a blind spot; a single feed that carries Upbit and Bithumb together closes it. For a strategy view of the two markets, see our blog write-up on Bithumb vs Upbit listing strategy and Bithumb caution & delisting alerts.

Push over WebSocket, not REST polling

Most Bithumb delisting trackers poll Bithumb's REST notice endpoint on a timer — often every 30 minutes, sometimes as tight as 60 seconds. On a delisting that interval is the worst-case delay: a removal notice that lands just after a poll sits unseen until the next cycle. CryptoListing.ws instead pushes the event to every connected client over WebSocket the instant Bithumb publishes it — no poll cadence to wait out, millisecond-class delivery of a structured message. Bithumb's own native market-data WebSocket streams prices for pairs that already trade; it does not carry notice-board announcements.

Message shape

Titles pass through verbatim, so Korean text arrives intact. Treat ticker as potentially comma-separated: one Bithumb notice can name several coins.

{
  "type": "announcement",
  "title": "[안내] TOKEN(TOKEN) 원화 마켓 거래지원 종료 안내",
  "ticker": "TOKEN",
  "publisher": "bithumb",
  "listingType": "spot_delisting",
  "detectedTimestampUs": 1710345000005000,
  "dispatchTimestampUs": 1710345000006000
}

Connect and filter to Bithumb

Authenticate with an X-API-Key header on the upgrade. Use the Tokyo endpoint and the ?cex=bithumb filter to receive Bithumb announcements only.

# pip install "websockets>=14"  — the header param is additional_headers
# (extra_headers was removed in websockets v14+)
import asyncio, json, websockets

API_KEY = "dsk_your_key_here"
WS_URL  = "wss://cryptolisting.ws?cex=bithumb"  # Tokyo, Bithumb only

async def run():
    headers = {"X-API-Key": API_KEY}
    async with websockets.connect(WS_URL, additional_headers=headers) as ws:
        async for raw in ws:
            msg = json.loads(raw)
            if msg.get("type") != "announcement":
                continue
            if msg["listingType"] in ("spot_delisting", "caution_released"):
                for ticker in msg["ticker"].split(","):
                    print(msg["listingType"], ticker, msg["title"])

asyncio.run(run())

Turning the signal into action

The value of a Bithumb delisting alert is entirely about what you do in the window after it fires. A spot_delisting notice sets a countdown: deposits and withdrawals wind down, the order book grows one-sided, and the discount tends to open early rather than at the effective date. If you hold the token, the announcement is your cue to exit while there is still depth; if you do not, it is a well-defined event to trade the reaction against, on Bithumb or on another venue that still lists the pair.

A caution_released reads the other way. A coin that had been under investment caution and clears it has just shed an overhang, and the release often marks the bottom of that stress rather than the start of more. Keeping a lightweight record of which tickers are currently flagged turns each release into a contextual signal instead of an isolated line — you know whether you are looking at a resolved scare or noise. In both cases the point is the same: react to the announcement, not to a poll that surfaces it minutes later.

FAQ

What is a Bithumb investment caution?

A risk-warning designation on a coin that keeps trading. It can be lifted (caution_released) or escalate to a delisting — a warning, not a removal in itself.

How fast do I get a Bithumb delisting alert?

The event is pushed the instant Bithumb publishes the notice — millisecond-class delivery of a structured JSON message rather than a poll snapshot. Microsecond-precision timestamps let you measure end-to-end performance yourself.

Does the feed cover Bithumb listings too?

Yes. Listings, caution releases and delistings arrive on the same connection, distinguished by listingType. See the Bithumb listing alert page and the full API reference.

What about Upbit and Binance delistings?

The same feed carries Upbit and Binance removals. The crypto delisting alerts overview ties all three exchanges together.