Binance Futures Listing Alert
A real-time alert for new Binance futures & perpetual listings. The moment Binance announces that a token gets a USDⓈ-M or COIN-M contract, our WebSocket pushes a structured JSON event — ticker, listing type, microsecond timestamps — straight to your bot. For derivatives traders, the perpetual is often the first tradable Binance venue for a new asset, and the announcement is where the move begins.
Why the futures listing is its own signal
Most listing trackers are built around the spot event: "Binance Will List TOKEN". But Binance's derivatives desk runs on a separate cadence. A new perpetual contract — say TOKENUSDT on USDⓈ-M — is frequently launched days or weeks ahead of any spot pair, and a large number of tokens trade on Binance only as perpetuals and never get a spot listing at all. If your strategy lives on Binance Futures, the futures_listing announcement is the event you actually care about, and treating it as a footnote to spot means reacting late or missing the launch entirely.
The announcement matters because a perpetual launch concentrates attention, liquidity and leverage on a fresh symbol in a very short window. Funding rates, open interest and the initial mark price all form in the minutes after the contract goes live. The traders positioned first are the ones who read the announcement — not the ones who noticed the new symbol appear in a market-data stream after the fact.
Spot vs futures listings on Binance
| Event | listingType | What it means |
|---|---|---|
| Spot listing | spot_listing | New spot trading pair (e.g. TOKEN/USDT on the spot book) |
| Futures listing | futures_listing | New perpetual or delivery contract on Binance Futures (USDⓈ-M / COIN-M) |
| Futures delisting | futures_delisting | Removal of an existing Binance Futures contract |
These are distinct events with distinct trade implications. A token can get a futures listing without a spot listing, a spot listing without futures, or both — often on different days. Because each announcement arrives as its own event with its own listingType, you decide which ones drive your strategy instead of collapsing everything into one "new coin" bucket.
How the alert works
CryptoListing.ws watches Binance's official announcement channel and broadcasts a structured JSON event the instant a new futures listing is published. Your bot holds one persistent WebSocket connection and receives the event as a push — there is no page to scrape and no interval to tune on your side. The feed is designed for automated derivatives systems that need the notification as early as possible.
| Property | Value |
|---|---|
| Endpoint | wss://cryptolisting.ws — full feed, AWS Tokyo (ap-northeast-1a). Add ?cex=binance to receive Binance only. |
| Auth | X-API-Key header on the WebSocket upgrade request |
| Format | Binary frames, UTF-8 JSON, microsecond-precision timestamps |
| Relevant listing types | futures_listing, futures_delisting (plus spot_listing, hodler_airdrop, etc.) |
| Dispatch latency | Ultra-low-latency — each event carries timestamps so you can measure end-to-end yourself |
Connect and filter for futures listings
# pip install "websockets>=14" — header param is additional_headers # (extra_headers was removed in websockets v14+) import asyncio, json, websockets API_KEY = "dsk_your_key_here" WS_URL = "wss://cryptolisting.ws?cex=binance" # Tokyo, Binance only async def run(): headers = {"X-API-Key": API_KEY} async with websockets.connect(WS_URL, additional_headers=headers) as ws: async for raw in ws: msg = json.loads(raw) if msg.get("type") != "announcement": continue if msg["listingType"] == "futures_listing": for ticker in msg["ticker"].split(","): print("NEW PERP:", ticker, msg["title"]) asyncio.run(run())
Message format
Every announcement is a single JSON object. The ticker field can be comma-separated when one notice covers several contracts, so always split it.
{
"type": "announcement",
"title": "Binance Futures Will Launch USDⓈ-M TOKEN Perpetual Contract",
"ticker": "TOKEN",
"publisher": "binance",
"listingType": "futures_listing",
"detectedTimestampUs": 1710345000005000,
"dispatchTimestampUs": 1710345000006000,
"abnormalDetectionLatency": false
}
The two microsecond timestamps let you compute dispatch and network latency independently: dispatchTimestampUs - detectedTimestampUs is our side, your_receive_time - dispatchTimestampUs is the network to your host. Bots co-located in AWS Tokyo see the lowest end-to-end figure to the Tokyo endpoint.
Who this is for
This alert is aimed at developers and derivatives traders running automated systems on Binance Futures: perpetual scalpers, funding-rate and basis strategies, market makers who want to quote a fresh symbol first, and risk systems that need to know the instant a contract is added or removed. If you also trade the spot side, pair this with the Binance WebSocket guide and the broader crypto listing API.
FAQ
What is a Binance futures listing?
It is the addition of a new perpetual or delivery contract on Binance's USDⓈ-M or COIN-M derivatives market. It is announced separately from spot, and for many tokens the perpetual goes live before — or instead of — any spot pair, making the futures announcement the first tradable Binance signal.
Does the futures listing come before spot?
Often. Binance regularly launches a perpetual for a token ahead of a spot pair, and some tokens only ever trade as perpetuals. Watching futures_listing as its own event means you don't wait on a later spot_listing that may never arrive.
How do I filter to just futures events?
Connect with ?cex=binance to receive Binance only, then branch on msg["listingType"] == "futures_listing" (and "futures_delisting") in your handler, as in the snippet above.
Can I also catch delistings and airdrops?
Yes — the same connection carries delistings, HODLer airdrops and Monitoring Tag events. Branch on listingType to route each type.
Get your API key
Contact us on Telegram to start streaming Binance futures listing alerts. See pricing & tiers, the full documentation, or the Binance listing alert overview.
Get API key on Telegram