Crypto Listing Announcement API

A real-time WebSocket API for crypto exchange listing announcements and notices. Connect and receive structured JSON alerts for Binance, Upbit, Bithumb and Robinhood listing notices.

API overview

CryptoListing.ws provides three WebSocket dispatch endpoints that stream real-time listing announcements and notices from multiple cryptocurrency exchanges. The API is designed for automated trading systems that need the fastest possible notification of new exchange listing announcements. Same API key authenticates on all three endpoints — pick by your bot's location.

Who this API is for

• Trading bots and quant teams that act on listing, delisting and caution events and need a machine-readable trigger.
• Developers of alert products and dashboards covering Binance, Upbit, Bithumb and Robinhood without maintaining one integration per exchange.
• Researchers who need timestamped announcement history: the free JSON feed and the latest listings archive, each announcement with its own page and price-reaction chart.
• Not writing a bot? You probably just want the alerts: follow the free Telegram channel or @cryptolistingws on X.

Free options

• SpeedTrial — free WebSocket key on the production feed with a +1 ms courtesy delay; ticker and title are redacted. Made for benchmarking. One-week key, renewable on request.
• FreeDelayed — free WebSocket key with the full feed, ticker and title included, and a +240 ms delay. One-week key, renewable on request.
• Public JSON feed — recent announcements as a static file, no key needed. Not a real-time stream.
• Telegram channel and X account — free human-readable alerts.

Paid tiers — Basic (+20 ms) and Premium (no delay) — are priced per exchange and per month in USDT: see pricing and the price calculator. Every key, free or paid, is issued on request on Telegram — there is no self-serve sign-up.

Official exchange announcement APIs vs this API

Binance and Upbit now publish their own announcement streams, and Bithumb exposes its notices over REST. They cost nothing beyond an exchange account (Bithumb needs none) and are a sound choice if you trade one exchange and are ready to parse titles yourself. As documented on 28 September 2026:

Use an official channel when you trade a single exchange and can maintain the parsing. Use this API when you want several exchanges behind one connection, a stable schema with the ticker and event type already extracted, delistings and caution releases classified, and Robinhood events. We do not publish a speed comparison with the official channels.

Sources (checked on 28 September 2026) — Public pages each fact about another service comes from, given as plain addresses:

• Binance — https://developers.binance.com/docs/cms/general-info · https://developers.binance.com/docs/cms/announcement
• Upbit — https://docs.upbit.com/kr/reference/websocket-announcement · https://docs.upbit.com/kr/changelog/websocket-announcement
• Bithumb — https://apidocs.bithumb.com/reference/%EA%B3%B5%EC%A7%80%EC%82%AC%ED%95%AD-%EC%A1%B0%ED%9A%8C

Message format

Every announcement message contains the ticker, exchange, listing type, and two microsecond-precision timestamps:

{
  "type": "announcement",
  "title": "Binance Will List TOKEN (TOKEN)",
  "ticker": "TOKEN",
  "publisher": "binance",
  "listingType": "spot_listing",
  "detectedTimestampUs": 1710345000005000,
  "dispatchTimestampUs": 1710345000006000
}

The full, up-to-date list of listingType values is documented in the message reference.

Exchange filtering

Use the ?cex= query parameter on the Tokyo endpoint to subscribe to specific exchanges only. The Seoul endpoint carries Upbit and Bithumb, so the same filter applies there. Robinhood is served only by the US endpoint, wss://us.cryptolisting.ws, which carries no other exchange.

wss://jp.cryptolisting.ws                    // Tokyo: Binance, Upbit, Bithumb — Robinhood is on wss://us.cryptolisting.ws
wss://jp.cryptolisting.ws?cex=binance        // Tokyo: binance only
wss://jp.cryptolisting.ws?cex=binance,upbit  // Tokyo: binance + upbit
wss://kr.cryptolisting.ws                    // Seoul: Upbit + Bithumb (ultra-fast from Korea)

Latency measurement

Every announcement includes two timestamps in microseconds since UNIX epoch. Calculate your latency:

dispatch_delay  = dispatchTimestampUs - detectedTimestampUs
network_delay   = your_receive_time  - dispatchTimestampUs
total_latency   = your_receive_time  - detectedTimestampUs

Why choose this listing announcement API?

Unlike REST-based polling APIs or Telegram bots, our WebSocket API delivers listing notices the instant they are detected. Zero-copy broadcast means the announcement message is serialized once and shared across all subscribers — no per-client serialization overhead. This architecture achieves consistent ultra-fast dispatch latency regardless of subscriber count. Read more about specific exchanges: Binance listing notices, Upbit listing announcements, Bithumb listing notices.

Building a bot? Follow the step-by-step Binance listing sniper bot tutorial in Python. There is also an Upbit & Bithumb listing bot tutorial in Python. The full API reference covers the WebSocket API, the message schema and Python, Node.js, Go and Rust code examples.

FAQ

What protocol does the API use?

WebSocket (RFC 6455) over TLS 1.2+. Authentication is done via the X-API-Key HTTP header on the upgrade request. Messages are UTF-8 JSON in binary frames. The same API key authenticates on all three endpoints — pick by your bot's location, not by the exchange you trade.

Which exchanges are supported?

Binance (spot listings, futures listings, delistings, HODLer airdrops, Monitoring Tag extend / remove), Upbit and Bithumb (KRW market spot listings, caution releases, and spot delistings — the trade-actionable stages of the Korean caution lifecycle), and Robinhood (Robinhood Listing and Robinhood Live events, served from wss://us.cryptolisting.ws). More exchanges are added based on subscriber demand. Use the ?cex= query parameter on the Tokyo endpoint to filter.

How do I authenticate?

Include the X-API-Key header in the WebSocket upgrade request. Get your key by contacting us on Telegram at @CLWfeed. The same key works on all three endpoints. See the Authentication docs for code samples.

What is the message latency?

Dispatch latency is ultra-fast. Each announcement carries microsecond-precision detectedTimestampUs and dispatchTimestampUs fields so you can independently measure end-to-end performance. Network latency depends on your bot's location: hosts in AWS Tokyo (ap-northeast-1a - apne1-az4) get the lowest end-to-end latency to the Tokyo endpoint, hosts in AWS Seoul (ap-northeast-2c - apne2-az3) to the Seoul endpoint, which carries Upbit and Bithumb, and hosts in AWS N. Virginia (us-east-1a - use1-az1) to the US endpoint, which carries Robinhood.

How do the three endpoints differ?

wss://jp.cryptolisting.ws (Tokyo) streams the full feed and is the default global endpoint. wss://kr.cryptolisting.ws (Seoul) streams Upbit and Bithumb and is optimized for trading bots co-located in Korea — it eliminates the Seoul→Tokyo network hop on the detection side. wss://us.cryptolisting.ws (N. Virginia) streams Robinhood only — Robinhood Listing and Robinhood Live events — for bots trading Robinhood. Connection caps and rate limits are tracked independently per endpoint.

What happens if the connection drops?

The server sends a heartbeat every 30 seconds; clients should send WebSocket pings on the same cadence. On disconnect, reconnect with exponential backoff (typically starting at 1s, doubling up to 30s). Listings emitted while you were disconnected are NOT replayed — for an audit trail of past detections, see latest detections.