All systems operational

Crypto listing announcements
before anyone else

Ultra-low latency WebSocket feed for real-time Binance, Upbit & Bithumb new coin listing notices.

Latest Listings and Delistings
CEX Ticker Type Detection Timestamp
Loading…
see all
Join Telegram Channel
WebSocket Endpoints
wss://cryptolisting.ws
Tokyo — global feed · Binance, Upbit & Bithumb
wss://kr.cryptolisting.ws
Seoul — Korea region · Upbit only — ultra-fast from Korea
Monitoring live
Binance
Live
Upbit
Live
Bithumb
Live
More soon
Coming soon
At a glance
μs precision
Dispatch latency
3 CEX
Live exchanges
24/7
Monitoring
What you get
Ultra-fast dispatch
From detection to your connection in real time. Zero-copy broadcast to all subscribers.
Microsecond timestamps
Precise timing at every stage: publish, detect, dispatch. Measure your exact latency.
Exchange filtering
Subscribe to specific exchanges with the ?cex= parameter. Receive only what you need.
Always-on heartbeat
30-second heartbeats with server timestamps. Know immediately if your connection drops.

Never miss a Binance listing alert again

Join our Telegram channel for updates, or contact us directly to get your API key and start trading new listings in real time. See our pricing & tiers to pick the plan that fits you.

Join Telegram Channel
Pick a tier
Free
0 ms
added delay
  • Test for an unlimited period of time
  • 0 ms added delay
  • title & ticker redacted on listings
Get a free key →
Premium
0 ms
added delay
  • Built for the best exec-time
  • 0 ms added delay
  • Full title & ticker — actionable
See pricing →
Basic
+20 ms
added delay
  • Built for speed, but at a lower cost
  • 20 ms added delay
  • Full title & ticker — actionable
See pricing →
Read the Documentation
See it in action
Example message 
{
  "type": "announcement",
  "title": "Binance Will List TOKEN",
  "ticker": "TOKEN",
  "publisher": "binance",
  "listingType": "spot_listing",
  "detectedTimestampUs": 1710345000005000,
  "dispatchTimestampUs": 1710345000006000
}
Quick start — Python 
# pip install websocket-client
import json, websocket

def on_message(ws, msg):
    d = json.loads(msg)
    if d["type"] == "announcement":
        print(f"{d['ticker']} on {d['publisher']}")

websocket.WebSocketApp(
    "wss://cryptolisting.ws",
    header=["X-API-Key: YOUR_KEY"],
    on_message=on_message,
).run_forever()
Frequently asked questions
How fast are the alerts?
Ultra-fast from detection to your WebSocket connection. That's faster than Telegram bots, email alerts, and even other WebSocket-based providers. Our purpose-built low-latency stack and co-located infrastructure gives us an edge no other provider can match.
How fast are you compared to competitors?

It depends on the exchange. For CEX with servers in Tokyo (Binance), our detection-to-dispatch is ultra-fast from wss://cryptolisting.ws. The Tokyo endpoint sits in the same AWS Tokyo region as Binance, so the round-trip is virtually zero.

For Korean exchanges, the announcement source is in Seoul, so the Tokyo endpoint carries an incompressible Seoul → Tokyo network hop on the detection side. To kill that hop entirely for Upbit, we operate a second dispatch endpoint in AWS Seoul: wss://kr.cryptolisting.ws. If your bot trades Upbit and is co-located in Korea, that endpoint puts you ultra-fast end-to-end. Bithumb is currently dispatched only from Tokyo (Seoul → Tokyo hop applies).

Our purpose-built infrastructure makes us consistently the fastest option available today across all monitored exchanges.

Where are your servers located?

We run a dual-region infrastructure. AWS Tokyo (ap-northeast-1a - apne1-az4) hosts our global endpoint wss://cryptolisting.ws, co-located with Binance's matching engine and serving the full feed (Binance + Upbit + Bithumb listings). AWS Seoul (ap-northeast-2c - apne2-az3) hosts a specialized Upbit-only endpoint wss://kr.cryptolisting.ws for Korea-based bots that want to bypass the Seoul↔Tokyo network hop.

For the absolute best performance, co-locate your bot with the exchange you trade on: AWS Tokyo for Binance bots, AWS Seoul for Upbit bots. Pair that with the matching endpoint and you get ultra-fast end-to-end — the maximum edge currently achievable for snipe-style trading on listing events.

Which exchanges do you monitor?
Binance, Upbit, and Bithumb are live now. More exchanges are being added regularly. You can filter by exchange using the ?cex=binance,upbit query parameter.
What types of announcements are detected?
Spot listings, futures listings, spot & futures delistings, HODLer Airdrops, Binance Monitoring Tag changes (extend / remove), Bithumb / Upbit caution releases and spot delistings (the trade-actionable stages of the Korean caution lifecycle), and other exchange announcements (maintenance, token swaps). Each message includes the announcement type so you can filter programmatically.
How do I connect?
Connect to wss://cryptolisting.ws (global feed: Binance, Upbit, Bithumb) or wss://kr.cryptolisting.ws (Seoul mirror — Upbit only, ultra-fast end-to-end from Korea) with your API key in the X-API-Key header. Same API key authenticates on both. You'll receive structured JSON messages instantly. Works with any WebSocket library in any language.
Can I use this for automated trading?
Yes. The API is designed specifically for trading bots. Every message is structured JSON with consistent field names, microsecond timestamps, and the ticker symbol ready for immediate execution.
How do I measure my latency?
Every announcement includes three timestamps: when the exchange published it, when we detected it, and when we dispatched it. Compare the dispatch timestamp to your receive time to calculate your exact network latency.
What if a listing has multiple tickers?
Some exchanges list multiple tokens in a single announcement. The ticker field will be comma-separated (e.g. ABC,DEF,GHI). Split on comma to get individual symbols.
How do I get an API key?
Contact us on Telegram @cryptolistingwebsocket. We'll set you up in minutes.
Which endpoint should I use — Tokyo or Seoul?

Pick by your bot's location, not by the exchange you trade. If your bot runs in AWS Tokyo / Asia-Pacific (Japan), use wss://cryptolisting.ws — it carries the full feed (Binance, Upbit, Bithumb). If your bot runs in AWS Seoul / Korea, use wss://kr.cryptolisting.ws — it carries Upbit announcements only and avoids the Seoul→Tokyo hop, giving ultra-fast end-to-end.

Same API key works on both endpoints. Pick one endpoint per bot based on its trading venue's region.

Ready to get low-latency WebSocket alerts?

Get your API key in minutes or explore the full documentation.

Contact on Telegram Read the Documentation