Bithumb listing WebSocket API for spot listings and delistings
Track Bithumb spot listings and trading-support terminations with the New Listings Feed low-latency WebSocket API. Each parsed event includes tickers and an original notice link, so your bot can route listing and delisting announcements separately.
$USELESS listed on Bithumb spot
— New Listings Feed (@NewListingsFeed) September 8, 2026
Bithumb events we send
Spot listings and trading-support terminations share the spot market type. The event field separates the two, so a spot subscription can support a listing handler and a separate delisting handler.
A spot listing alert reports the trading-support announcement. Trading can open later, as the AVA record below shows. Read the notice's opening time separately from the alert's detection time.
Scroll horizontally to compare all columns.
| Notice | event | type |
|---|---|---|
| New trading support | listing | spot |
| Trading support terminated | delisting | spot |
Real Bithumb notices
This recorded /v2/fast Bithumb event took 137µs (0.137ms) from detection to publication.
The historical listings below have illustrative v2 full JSON excerpts for paid keys, including recorded contract data. Those excerpts omit event IDs, timestamps and market metrics. Dates are publication dates in UTC.
The DEBIT and USELESS excerpts have no confirmed contract. Their suggested_match entries show candidate matches separately.
- /v2/fast · $AVA added to Bithumb KRW market · 0.137ms processing
v2 JSON example
{ "id": 3665121157470208, "type": "announcement", "exchange": "bithumb", "text": "트라발라(AVA) 원화 마켓 추가", "url": "https://feed.bithumb.com/notice/1654884", "detected_time_us": 1789609940171560, "sent_time_us": 1789609940171697 } - $DEBIT listed on Bithumb spot
v2 JSON example
{ "type": "announcement", "url": "https://feed.bithumb.com/notice/1654813", "content": { "title": "텔러파이낸스(DEBIT) 원화 마켓 추가" }, "parser": { "exchange": "bithumb", "classification": { "event": "listing", "type": "spot", "category": "crypto" }, "display": "$DEBIT listed on Bithumb spot", "assets": [ { "symbol": "DEBIT", "contracts": [], "suggested_match": { "confidence": "high", "project_name": "Teller", "suggested_contracts": [ { "chain": "bsc", "contract": "0x66661c7229901f568f16bd1551b3ba826f83ce49" } ] } } ] } } - $USELESS listed on Bithumb spot
v2 JSON example
{ "type": "announcement", "url": "https://feed.bithumb.com/notice/1654782", "content": { "title": "유즈리스(USELESS) 원화 마켓 추가" }, "parser": { "exchange": "bithumb", "classification": { "event": "listing", "type": "spot", "category": "crypto" }, "display": "$USELESS listed on Bithumb spot", "assets": [ { "symbol": "USELESS", "contracts": [], "suggested_match": { "confidence": "high", "project_name": "Useless Coin", "suggested_contracts": [ { "chain": "solana", "contract": "Dz9mQ9NzkBcCsuGPFJ3r1bS4wgqKMHBPiVuniW8Mbonk" } ] } } ] } }
Raw notices or parsed Bithumb listings
Use /v2/fast?exchange=bithumb&data_type=announcement when your bot parses the raw announcement title itself. STARTER and PRO keys can use this stream. /v2/full provides New Listings Feed's parsed tickers and event classifications, with available onchain data on paid keys.
A Korean notice can identify a token by its local project name and ticker. In the published DEBIT and USELESS examples, parser.assets gives your client the ticker, while content.title and url preserve the original notice reference. Suggested contracts remain labeled as candidate matches.
Filter listings or delistings
Connect to /v2/full?exchange=bithumb&market_type=spot. This receives both spot listings and delistings. Select the event you want with parser.classification.event.
The example accepts listing. Change that check to delisting to handle trading-support terminations. Read each ticker from parser.assets.
Node.js: Bithumb spot listings
Install ws, set NLF_API_KEY to your key, and save the example as bithumb-listings.cjs. Run node bithumb-listings.cjs. The output includes each ticker, the original notice title and its URL.
This example uses the FREE endpoint with a 3-second configured delay. For STARTER or PRO, use a regional host from the connection reference.
// npm install ws
const WebSocket = require("ws");
if (!process.env.NLF_API_KEY) {
throw new Error("Set NLF_API_KEY before starting the client.");
}
const ws = new WebSocket(
"wss://ws.newlistings.pro/v2/full?exchange=bithumb&market_type=spot",
{ headers: {
authorization: `Bearer ${process.env.NLF_API_KEY}`
} }
);
ws.on("message", raw => {
const message = JSON.parse(raw.toString());
if (message.type === "error") {
console.error(message.code, message.message);
return;
}
const classification = message.parser?.classification;
if (classification?.event !== "listing") return;
for (const asset of message.parser.assets) {
console.log({
id: message.id,
symbol: asset.symbol,
type: classification.type,
title: message.content?.title,
url: message.url
});
}
});
ws.on("error", error => console.error(error.message));Fields to use in your client
Read parser.assets for the tickers. A notice can contain several assets, so loop through the array. When available, content.title carries the original announcement title; url links to the source.
parser.classification.event tells you whether it is a listing or delisting. parser.classification.type tells you the market or product. parser.display is the readable summary.
Receive Upbit and Bithumb listings on one socket
Connect to /v2/full?exchange=upbit,bithumb&data_type=announcement&market_type=spot and check parser.exchange to route each notice. Read parser.classification.event before sending it to a listing or delisting handler.
The documented parser.classification.markets field applies to Upbit spot listings. Do not copy the Upbit KRW predicate onto every Bithumb event: the Bithumb examples here omit that field. Use the Bithumb classification and notice context for your Bithumb rules.
Find the fastest Bithumb listing feed for your bot
For Bithumb announcements, connect directly to our dedicated AWS Tokyo WebSocket: wss://tokyo.newlistings.pro/v2/fast for raw notices or wss://tokyo.newlistings.pro/v2/full for parsed events. STARTER and PRO also include New York and Seoul; compare arrivals from your bot server.
New Listings Feed is the fastest crypto listing WebSocket for bots and listing snipers, optimized for ultra-low latency. Compare Bithumb notices received on your own bot server. Match the original notice and event type, then compare arrival time alongside the fields your handler actually uses.
FREE includes a 3-second configured delay for integration testing. A comparison of PRO delivery requires a PRO capture at zero configured delay. Your client still has network and processing time.
Paid keys include token contracts, project matches and onchain market data when available. Exchange-published contracts and inferred matches remain separately labeled in the event.
Keep reading
- Exchanges
- Binance new listings and Alpha alerts over WebSocket
- The fastest Upbit listing WebSocket for bots and snipers
- Robinhood asset additions and spot listings
- Coinbase new listings and roadmap alerts over WebSocket
- WebSocket performance
- Measure listing WebSocket delivery from your bot server
- Onchain data for crypto listing and sniping bots
- The fastest crypto listing WebSocket, measured from your server
- The fastest listing feed for crypto sniper bots
- Listing announcement WebSockets and market-data WebSockets
- Crypto listing alerts on Telegram and WebSocket
- Receive crypto listing alerts in Node.js
- New Listings Feed vs other listing services
- Crypto alerts for listings, prices, whales and news
- The fastest Binance Alpha listing WebSocket for bots and snipers