Robinhood Listing Alert

Get Robinhood crypto listing alerts in real time — Robinhood Listing, when a token is added to Robinhood but not tradable yet on Robinhood, and Robinhood Live, when it becomes tradable on Robinhood. Two event types, pushed over WebSocket from a dedicated US endpoint.

Why Robinhood crypto listings move markets

Robinhood is the largest retail brokerage app in the United States, and its crypto section puts one-tap buying in front of millions of US investors who do not use offshore exchanges. When a token becomes tradable on Robinhood, a large pool of buyers who previously had no easy way to purchase it suddenly can — and that demand shows up on the order books of the exchanges where the token already trades.

What makes Robinhood different from the other publishers we cover is that it publishes no listing notice. Two moments can be observed instead: a token is added to Robinhood but is not tradable yet on Robinhood (Robinhood Listing), and the token becomes tradable on Robinhood (Robinhood Live). The first is not a promise that trading will open on Robinhood — for some tokens trading opened minutes later, for others weeks later, and some never opened at all — so we report them as two separate event types.

Two Robinhood event types: Robinhood Listing and Robinhood Live

Robinhood events come as two message types with the same JSON envelope, distinguished by the listingType field:

• wallet_listing — Robinhood Listing, not tradable yet on Robinhood. The token has been added to Robinhood but cannot be bought or sold there yet. Trading may open minutes, days or weeks later — or never.
• cex_listing — Robinhood Live, tradable on Robinhood. Trading is open on Robinhood. This is the event that exposes the token to US retail order flow.

A wallet_listing (Robinhood Listing), as it arrives on the wire:

{
  "type": "announcement",
  "publisher": "robinhood",
  "listingType": "wallet_listing",
  "ticker": "PONS",
  "title": "Robinhood: PONS (Pons to US Dollar) — added to Robinhood assets",
  "detectedTimestampUs": 1757570000123456,
  "dispatchTimestampUs": 1757570000123999,
  "abnormalDetectionLatency": false
}

And a cex_listing (Robinhood Live), when the token becomes tradable on Robinhood — title ending in tradable on Robinhood:

{
  "type": "announcement",
  "publisher": "robinhood",
  "listingType": "cex_listing",
  "ticker": "XYZ",
  "title": "Robinhood: XYZ (XYZ to US Dollar) — tradable on Robinhood",
  "detectedTimestampUs": 1757829200456789,
  "dispatchTimestampUs": 1757829200457301,
  "abnormalDetectionLatency": false
}

Robinhood message format

The envelope is identical to every other publisher on CryptoListing.ws, so a handler written for Binance or Upbit parses Robinhood messages unchanged. type is always announcement; publisher is robinhood; listingType is wallet_listing or cex_listing; ticker is the asset symbol; title is a human-readable line that ends in added to Robinhood assets or tradable on Robinhood. detectedTimestampUs and dispatchTimestampUs are microsecond Unix timestamps, and abnormalDetectionLatency flags a message our own monitoring considers late, so you can gate automated actions on it. Field semantics are documented in the documentation.

How to get Robinhood listing alerts

Connect to the US endpoint with your API key in the X-API-Key header. The ?cex=robinhood filter is accepted and optional there — the US endpoint carries Robinhood only — and branching on listingType separates the two event types:

# Robinhood listings (US endpoint)
import json, websocket

def on_message(ws, msg):
    data = json.loads(msg)
    if data["type"] != "announcement":
        return
    if data["listingType"] == "wallet_listing":
        print(f"ROBINHOOD LISTING: {data['ticker']}")  # Robinhood Listing: not tradable yet on Robinhood
    elif data["listingType"] == "cex_listing":
        print(f"ROBINHOOD LIVE: {data['ticker']}")     # Robinhood Live: tradable on Robinhood
        # Execute your trade here

websocket.WebSocketApp(
    "wss://us.cryptolisting.ws?cex=robinhood",
    header=["X-API-Key: YOUR_KEY"],
    on_message=on_message,
).run_forever()

The US endpoint — and where it sits next to Tokyo and Seoul

Robinhood is dispatched from a third AWS region. The same API key works on all three endpoints, and each endpoint carries its own set of publishers — there is no overlap for Robinhood:

• N. Virginia — wss://us.cryptolisting.ws — Robinhood only, hosted in AWS us-east-1. Best if your bot lives in the eastern United States. ?cex=robinhood is accepted but optional here.
• Tokyo — wss://jp.cryptolisting.ws — Binance, Upbit, Bithumb. Does not carry Robinhood.
• Seoul — wss://kr.cryptolisting.ws — Upbit, Bithumb. Does not carry Robinhood.

A single bot can hold one long-lived WebSocket per endpoint. If your bot already runs in Tokyo or Seoul for the Asian exchanges, keep it there and simply add a connection to the US endpoint:

# One bot, three regions — same key on every endpoint
"wss://jp.cryptolisting.ws?cex=binance,upbit,bithumb"   # Tokyo
"wss://kr.cryptolisting.ws?cex=upbit,bithumb"           # Seoul
"wss://us.cryptolisting.ws?cex=robinhood"               # N. Virginia

Robinhood listing detection speed

We monitor Robinhood around the clock. When a token is added to Robinhood we push the wallet_listing event (Robinhood Listing) to every connected subscriber, and when it becomes tradable on Robinhood we push the cex_listing event (Robinhood Live) — structured and deduplicated, as soon as it is detected. Robinhood does not announce new listings, so there is no official notice to subscribe to; a WebSocket push removes the human from the loop.

Our edge comes from the same purpose-built low-latency infrastructure that serves the Binance and Korean feeds — optimized at every layer, no unnecessary overhead — now deployed in the US region closest to Robinhood's users. The free SpeedTrial tier lets you measure real end-to-end timing from your own infrastructure.

Robinhood vs Binance listing announcements

Both events move prices, but they are shaped differently. Binance listing announcements are formal notices published ahead of trading, on a globally accessible exchange — the market reacts to the notice itself. Robinhood listings have no public notice: what can be observed is a token being added to Robinhood (Robinhood Listing) and, for some tokens, becoming tradable on Robinhood later (Robinhood Live). The delay varies from minutes to weeks and the first event does not guarantee the second, so each is reported as its own event type.

Multi-exchange monitoring

You don't have to choose. The publisher field tells your bot which exchange each message came from, so one handler can serve Robinhood and Binance together. Because Robinhood lives on its own endpoint, combining them means two connections rather than one filter:

"wss://jp.cryptolisting.ws?cex=binance"   # Tokyo — Binance
"wss://us.cryptolisting.ws?cex=robinhood" # N. Virginia — Robinhood

On the Tokyo endpoint, leave the cex parameter empty to receive listing announcements from all monitored Asian exchanges (Binance, Upbit, Bithumb). Subscribing to two or more exchanges unlocks bundle pricing. See the full API reference for details.

Robinhood listing WebSocket API

Developer guide: Robinhood WebSocket for listing announcements · background: Robinhood Crypto Listings: Robinhood Listing vs. Robinhood Live.

Stream Robinhood crypto listings over our real-time WebSocket API. Each Robinhood Listing and each Robinhood Live event arrives as structured JSON with microsecond timestamps, ready for your bot — the same schema as Binance, Upbit and Bithumb, from a dedicated endpoint in AWS N. Virginia.

Frequently asked questions

What is the difference between wallet_listing and cex_listing on Robinhood?

wallet_listing (Robinhood Listing) means a token has been added to Robinhood but is not tradable yet on Robinhood: it cannot be bought or sold there yet. cex_listing (Robinhood Live) means the token is tradable on Robinhood. A wallet_listing is not a promise that trading will open on Robinhood: some tokens have become tradable minutes later, others weeks later, and some never. Both events share the same JSON envelope and the same ticker field, so a bot can match a cex_listing to an earlier wallet_listing when there is one.

Do the Tokyo or Seoul endpoints carry Robinhood announcements?

No. On the WebSocket API, Robinhood is served only by the US endpoint, wss://us.cryptolisting.ws, hosted in AWS N. Virginia (us-east-1). The Tokyo endpoint (wss://jp.cryptolisting.ws) carries Binance, Upbit and Bithumb; the Seoul endpoint (wss://kr.cryptolisting.ws) carries Upbit and Bithumb. Your existing API key works on all three, so add a second connection to the US endpoint rather than changing your Tokyo or Seoul filters. Robinhood events are also posted on our public Telegram channel and X account, and listed on latest listings.

How much do Robinhood listing alerts cost?

Robinhood is priced like Upbit: Basic is 400 USDT per month and Premium is 750 USDT per month. Two free tiers exist — SpeedTrial (redacted payload with a small added delay, for benchmarking) and FreeDelayed (the full feed, delivered with a fixed delay; first month free, then 200 USDT per month, all exchanges included). Bundles lower the monthly price: 2 exchanges −50 USDT on Basic / −100 on Premium, 3 exchanges −100 / −150, and all 4 exchanges on Premium for 1900 USDT per month. Prepaying 3, 6 or 12 months saves 15%, 22.5% or 30%; bundle and duration discounts do not stack. Full details on the pricing page.

Can I combine Robinhood and Binance alerts?

Yes. Open one WebSocket to the Tokyo endpoint with ?cex=binance and a second one to the US endpoint with ?cex=robinhood, using the same API key on both. Every message carries a publisher field (binance or robinhood) and the same schema, so one handler routes both streams to the right venue. Bundle pricing applies as soon as you subscribe to two or more exchanges.

Why do Robinhood crypto listings matter for traders?

Robinhood gives millions of US retail investors one-tap access to crypto. When an asset becomes tradable on Robinhood, a large pool of US buyers who could not easily buy it before suddenly can, and that demand can move the price on other venues. CryptoListing.ws reports Robinhood Listing (the token is added to Robinhood, not tradable yet on Robinhood) and Robinhood Live (the token is tradable on Robinhood) as separate events, so a bot can follow each token from its first Robinhood event.

Where should I host my bot for the Robinhood feed?

The Robinhood feed is dispatched from AWS N. Virginia (us-east-1). Hosting your bot in the same region minimises the network hop from our dispatcher to your client. If your bot already runs in Tokyo or Seoul for the Asian exchanges, keep it there and open an extra connection to wss://us.cryptolisting.ws — one long-lived WebSocket per endpoint is the recommended setup. The free SpeedTrial tier lets you measure end-to-end timing from your own infrastructure before choosing a plan.