Upbit listing alerts
Receive Upbit listing announcements, trading-support terminations and caution notices over WebSocket. Filter KRW listings using the parsed market field, with the original Korean title and notice URL alongside the tickers.
Upbit events we send
Scroll horizontally to compare all columns.
| Notice | event | type |
|---|---|---|
| New trading support | listing | spot |
| Trading support terminated | delisting | spot |
| Investment caution notice | delisting | caution-spot |
Low-latency Upbit listing alerts
Our low-latency detection covers Upbit and the other supported exchanges. /v2/fast sends the raw notice before parsing; /v2/full sends the classified event for your trading client.
Real Upbit notices
Published listings with illustrative v2 full JSON excerpts for paid keys, including contract data recorded in Tokyo. Event IDs, timestamps and market metrics are omitted. Dates are publication dates in UTC.
- $BFC listed on Upbit spot (KRW)
v2 JSON example
{ "type": "announcement", "url": "https://upbit.com/service_center/notice?id=250738258", "content": { "title": "바이프로스트(BFC) KRW, USDT 마켓 디지털 자산 추가" }, "parser": { "exchange": "upbit", "classification": { "event": "listing", "type": "spot", "category": "crypto", "markets": [ "krw" ] }, "display": "$BFC listed on Upbit spot (KRW)", "assets": [ { "symbol": "BFC", "contracts": [], "suggested_match": { "confidence": "high", "project_name": "Bifrost", "suggested_contracts": [ { "chain": "ethereum", "contract": "0x0c7d5ae016f806603cb1782bea29ac69471cab9c" } ] } } ] } } - $REZ listed on Upbit spot
v2 JSON example
{ "type": "announcement", "url": "https://upbit.com/service_center/notice?id=26668186", "content": { "title": "렌조(REZ) 신규 거래지원 안내 (USDT 마켓)" }, "parser": { "exchange": "upbit", "classification": { "event": "listing", "type": "spot", "category": "crypto", "markets": [ "usdt" ] }, "display": "$REZ listed on Upbit spot", "assets": [ { "symbol": "REZ", "contracts": [], "suggested_match": { "confidence": "high", "project_name": "Renzo", "suggested_contracts": [ { "chain": "ethereum", "contract": "0x3b50805453023a91a8bf641e279401a0b23fa6f9" } ] } } ] } } - $HEMI, $USELESS listed on Upbit spot
v2 JSON example
{ "type": "announcement", "url": "https://upbit.com/service_center/notice?id=155358260", "content": { "title": "헤미(HEMI), 유즈리스(USELESS) 신규 거래지원 안내 (BTC, USDT 마켓)" }, "parser": { "exchange": "upbit", "classification": { "event": "listing", "type": "spot", "category": "crypto", "markets": [ "btc", "usdt" ] }, "display": "$HEMI, $USELESS listed on Upbit spot", "assets": [ { "symbol": "HEMI", "contracts": [] }, { "symbol": "USELESS", "contracts": [], "suggested_match": { "confidence": "high", "project_name": "Useless Coin", "suggested_contracts": [ { "chain": "solana", "contract": "Dz9mQ9NzkBcCsuGPFJ3r1bS4wgqKMHBPiVuniW8Mbonk" } ] } } ] } }
Filter KRW listings
Connect to /v2/full?exchange=upbit&type=spot. In your client, accept event = listing and check that parser.classification.markets includes krw. Values in markets are lowercase.
The socket filters by exchange and type. The KRW check runs in your client. If markets is missing, the example skips the event. Remove the KRW check to receive all parsed Upbit spot listings.
To receive caution notices too, subscribe with type=spot,caution-spot. The example below handles KRW listings only. For cautions, also accept event = delisting with type = caution-spot without requiring a KRW market. Trading-support terminations use event = delisting with type = spot.
Node.js: KRW listings only
Install ws, set NLF_API_KEY to your key, and run this example. It prints each ticker with its notice URL and original title.
// npm install ws
const WebSocket = require("ws");
const ws = new WebSocket(
"wss://tokyo.newlistings.pro/v2/full?exchange=upbit&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;
if (!classification.markets?.includes("krw")) return;
for (const asset of message.parser.assets) {
console.log({
id: message.id,
symbol: asset.symbol,
type: classification.type,
markets: classification.markets,
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. 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.