Exchange Listing Monitor — new coin listings & delistings from 7 CEXs

New coin listing and delisting announcements from Binance, Upbit, Bithumb, OKX, Bybit, KuCoin and Kraken, in one deduped feed. Each scheduled run emits only the announcements it has never seen before, already classified as a listing or a delisting, with the tickers pulled out of the title.

Keyless official venue announcement APIs — no exchange account, no API key, no Playwright.

Read this before you buy: latency

This is a scheduled poller, not a websocket. Freshness equals your schedule interval: on a 5-minute schedule an announcement reaches you within roughly 0-5 minutes of the venue publishing it. That is fast enough to be first into a research pipeline, a Slack/Telegram alert, a watchlist, or a slower systematic strategy. It is not co-located front-running infrastructure, and nothing in this listing should be read as promising sub-second delivery. None of these seven venues publish a keyless push channel for announcements, so no polling actor can honestly claim otherwise.

Example output

One real record, exactly as pushed to the dataset:

{
  "venue": "okx",
  "announcementId": "okx-to-list-spkusd-x-perp",
  "title": "OKX to list SPKUSD X-Perp",
  "eventType": "listing",
  "symbols": ["SPK"],
  "publishedAt": "2026-08-28T03:00:09Z",
  "url": "https://www.okx.com/help/okx-to-list-spkusd-x-perp",
  "venueCategory": "announcements-new-listings",
  "detectedAt": "2026-08-31T12:07:00Z"
}

A Korean venue record — the title stays verbatim, and eventType plus symbols make it usable without translating anything:

{
  "venue": "bithumb",
  "announcementId": "1654694",
  "title": "인터폴드(FOLD), 이유알코인(EURC) 원화 마켓 추가",
  "eventType": "listing",
  "symbols": ["FOLD", "EURC"],
  "publishedAt": "2026-08-28T02:11:27Z",
  "url": "https://feed.bithumb.com/notice/1654694",
  "venueCategory": "마켓 추가",
  "detectedAt": "2026-08-31T12:07:00Z"
}

Fields

Field	What it is
venue	binance / upbit / bithumb / okx / bybit / kucoin / kraken
announcementId	Stable id unique within the venue — the dedupe key
title	The venue's headline, verbatim and untranslated
eventType	listing, delisting or unknown (see below)
symbols	Tickers named by the title, upper-cased, quote suffix stripped (ACXUSDT → ACX). [] when nothing is nameable
publishedAt	When the venue published it, ISO-8601 UTC (Korean venues converted from KST)
url	Link to the announcement on the venue's own site
venueCategory	The venue's own channel label, verbatim — filter looser than we do
detectedAt	When the monitor first saw it

Venues covered

Venue	Region	Channel
Binance	global	"New Cryptocurrency Listing" + "Delisting" announcement catalogs
Upbit	KR	Trading notices — the biggest listing-pump venue
Bithumb	KR	Public notices
OKX	global	New listings + delistings announcements
Bybit	global	New listings + delistings announcements
KuCoin	global	New listings + delistings announcements
Kraken	global	Blog "Asset Listings" posts

One venue being temporarily unreachable degrades to a warning in the log and the other six still emit. Only if every selected venue fails does the run fail — a dead run must never look like a quiet market.

Input options

Input	Default	What it does
venues	all seven	Which announcement channels to poll
eventTypes	all	Filter to listing, delisting and/or unknown
symbols	all	Ticker watchlist, e.g. ["PEPE","WIF","ARB"]
sinceHours	48	First-run backfill window in hours; later runs emit only unseen announcements
maxItems	300	Cap per run, split fairly across the venues that have announcements so a busy venue cannot crowd out the rest. Records over the cap are not marked seen, so they emit next run — nothing is lost
userAgent	browser default	Rarely needed; several venues 403 bare non-browser clients

How eventType is decided — and why it is cautious

eventType comes from the announcement title, never from the channel it arrived on, because those channels are noisy in ways that would cost you money:

• Bybit's "New Listings" channel carries prize-pool promotions.
• Binance's "Delisting" catalog carries routine margin-pair housekeeping.
• Upbit's caution designation (거래 유의 종목 지정 / "Investment Warning") frequently precedes a delisting without being one.
• OKX's delistings channel carries token-migration notices.

Anything the title does not clearly say is unknown — and the venue's own label survives in venueCategory, so if you want a looser rule you can build it from the raw data rather than un-pick ours.

symbols is cautious the same way: parenthesised tickers win, ALLCAPS tokens are taken only from titles already classified as a listing or delisting, and titles that name no ticker ("Bybit to Delist 1 Trading Pair(s)", "KuCoin Will Delist Certain Projects") or name it in Chinese characters return [] rather than a guess. An empty array falls back to the title; a wrong ticker fires a wrong trade.

Use cases

"Alert me the moment a coin I hold gets a delisting notice." Schedule every 5-15 minutes with eventTypes: ["delisting"] and your holdings in symbols. Wire the dataset to Slack, Telegram or Discord via an Apify integration. Delisting notices move price hard and the venues do not email you.

"Feed my listing-arb / momentum bot every new CEX listing." Default inputs, eventTypes: ["listing"], schedule every 5 minutes. Each dataset item is a fresh, deduped event with the ticker already extracted, so your bot consumes rows instead of scraping seven announcement pages and writing seven parsers.

"Track which venues are listing our token, and our competitors'." Put your ticker and your comparables in symbols and leave eventTypes empty. You get a dated, sourced record of every venue announcement naming them — useful for BD reporting, exchange-relations decks, and spotting a competitor's Upbit or Binance listing the day it lands.

Update & maintenance promise

Venue payload shapes are checked weekly and the parsers are covered by 125 offline tests running against trimmed real captures from all seven venues. Schema drift logs a clear named warning instead of crashing a run, and a venue whose API changes degrades to a warning while the rest keep emitting.

Known limits (stated up front)

• Latency is your schedule interval, not milliseconds. See above.
• Kraken publishes 10 blog posts per feed page with no paging, and Bithumb's API caps at 20 notices with no paging — roughly one week each. A very large sinceHours cannot invent history those two venues do not publish. Binance, Upbit, OKX, Bybit and KuCoin page back much further.
• Korean titles ship untranslated. Upbit renders most notices in English; Bithumb and some Upbit notices stay Korean. eventType and symbols are the machine-readable layer over both.
• Coinbase and Gate.io are not in v1. Coinbase publishes no keyless announcement feed (its blog is a JavaScript app and the old RSS paths redirect), and Gate.io's announcement endpoint is edge-blocked. Both are tracked for v1.1.
• Some announcement pages are bot-protected against non-browser clients (Binance returns an empty 202, Bithumb's feed host sits behind Cloudflare). They open normally in a browser. The monitor never fetches them — it only emits the link.

Pricing (pay-per-event)

Event	Price
Actor start	$0.005 per run
Venue polled	$0.001 per venue successfully polled (a failed venue is not charged)
Listing announcement detected	$0.02 per new announcement record

A steady-state 5-minute schedule usually emits nothing and costs $0.012 a run. You pay for events, not for polling noise.

Changelog

• 0.1.1 — maxItems is now split fairly across the venues that returned announcements instead of being consumed first-come-first-served. With a small cap the first venue polled could take the whole allowance and the other six emitted nothing in that run; now every contributing venue gets its share and the unused share of a quiet venue is handed back to the busy ones. No change to record fields, inputs, state or pricing.
• 0.1 — first release. Seven venues (Binance, Upbit, Bithumb, OKX, Bybit, KuCoin, Kraken), conservative title-based listing/delisting classification, ticker extraction, hour-precision backfill window, per-venue failure degradation.