Robinhood asset additions and spot listings

New Listings Feed was the first to detect Robinhood's asset-catalog additions. Our $JUGGERNAUT and $FRONG alert on 10 September 2026 brought industry-wide attention to this category. Our WebSocket delivers both asset additions and live spot listings directly to trading bots through our ultra-low-latency WebSocket API.

JUGGERNAUT and FRONG rose as much as 500% and 130% after their asset-page additions, while CASHCAT briefly gained 151% following its August spot listing.

$JUGGERNAUT, FRONG added to Robinhood assets
— New Listings Feed (@NewListingsFeed) September 10, 2026

Robinhood events we send

We detect two Robinhood categories. assets means a token has appeared in Robinhood's asset catalog. spot means Robinhood has opened trading for it. An asset addition does not confirm spot availability.

Parsed events identify the category and affected tickers. Select spot, assets, or both on one WebSocket connection. Both use event: listing, with the category in parser.classification.type.

Scroll horizontally to compare all columns.

Values in `parser.classification`
Notice	event	type
Spot listing	listing	spot
Asset-catalog discovery	listing	assets

Robinhood listing alerts over WebSocket

New Listings Feed sends Robinhood notices through two WebSocket streams. /v2/fast carries the raw announcement text for clients with their own parser. /v2/full adds the spot or assets classification and ticker symbols, with available onchain data on STARTER and PRO. New Listings Feed provides the event data; your own system handles execution.

Scroll horizontally to compare all columns.

How Robinhood listing alerts arrive
Approach	What arrives
`/v2/fast`	Raw Robinhood title as soon as we detect it
`/v2/full`	Classified `spot` or `assets` events and ticker symbols, with available contracts, suggested matches and metrics on STARTER and PRO

Recorded Robinhood detection time

We detected $JUGGERNAUT, $FRONG added to Robinhood assets on 10 September 2026 at 12:29:34.749 UTC.

For Robinhood, the New York edge receives the notices first. Connect directly to our New York WebSocket on AWS US East: wss://ny.newlistings.pro/v2/fast for raw notices or wss://ny.newlistings.pro/v2/full for parsed events. STARTER and PRO include this regional endpoint.

Raw and parsed Robinhood examples

This recorded /v2/fast Robinhood event took 169µs (0.169ms) from detection to publication.

/v2/fast carries the raw title. /v2/full carries the classified event and available contract data.

In the JUGGERNAUT and FRONG record, Full includes suggested Robinhood Chain contracts for both assets. They appear under suggested_match.suggested_contracts, with a confidence label for each match.

The JUGGERNAUT and FRONG excerpts are illustrative; event IDs, timestamps and market metrics are omitted. The suggested contracts are recorded from this listing.

Sep 14, 2026/v2/fast · $INDEX added to Robinhood assets · 0.169ms processing

v2 JSON example

{
  "id": 3664719874867200,
  "type": "announcement",
  "exchange": "robinhood",
  "text": "New Robinhood US asset discovered (not tradable yet): $INDEX",
  "url": "https://robinhood.com/us/en/crypto/",
  "detected_time_us": 1789414001400601,
  "sent_time_us": 1789414001400770
}

Sep 10, 2026/v2/full · $JUGGERNAUT, $FRONG added to Robinhood assets

v2 JSON example

{
  "type": "announcement",
  "url": "https://robinhood.com/us/en/crypto/",
  "content": {
    "title": "New Robinhood US asset discovered (not tradable yet): $JUGGERNAUT, $FRONG"
  },
  "parser": {
    "exchange": "robinhood",
    "classification": {
      "event": "listing",
      "type": "assets",
      "category": "crypto"
    },
    "display": "$JUGGERNAUT, $FRONG added to Robinhood assets",
    "assets": [
      {
        "symbol": "JUGGERNAUT",
        "contracts": [],
        "suggested_match": {
          "confidence": "medium",
          "project_name": "The Juggernaut",
          "suggested_contracts": [
            {
              "chain": "robinhood",
              "contract": "0xd7321801caae694090694ff55a9323139f043b88"
            }
          ]
        }
      },
      {
        "symbol": "FRONG",
        "contracts": [],
        "suggested_match": {
          "confidence": "high",
          "project_name": "frong",
          "suggested_contracts": [
            {
              "chain": "robinhood",
              "contract": "0x6245e67affa44a23077f0ea7f981a8dc743a0c47"
            }
          ]
        }
      }
    ]
  }
}

Sep 10, 2026/v2/fast · $JUGGERNAUT, $FRONG added to Robinhood assets

v2 JSON example

{
  "type": "announcement",
  "exchange": "robinhood",
  "text": "New Robinhood US asset discovered (not tradable yet): $JUGGERNAUT, $FRONG",
  "url": "https://robinhood.com/us/en/crypto/"
}

Choose Robinhood spot or assets

Use exchange=robinhood&market_type=spot for tradable listings. Use market_type=assets for catalog discoveries. Combine them with market_type=spot,assets.

FREE can receive parsed Robinhood spot listings on wss://ws.newlistings.pro/v2/full. Asset-catalog events and onchain enrichment require STARTER or PRO. For paid Robinhood streams, use wss://ny.newlistings.pro/v2/full?exchange=robinhood&market_type=spot,assets.

market_type matches parser.classification.type in full. Check that field in the client if one socket receives both. Fast accepts exchange=robinhood but has no market_type filter because it sends notices before classification.

Current market filters and coverage

Node.js: Robinhood Full listings

Install ws, set NLF_API_KEY to your key, and save the example as robinhood-listings.cjs. Run node robinhood-listings.cjs. This example connects to the FREE Full host and logs parsed spot listings. For asset additions or onchain fields, use a STARTER or PRO key with ny.newlistings.pro, then select market_type=assets or market_type=spot,assets.

// npm install ws
const WebSocket = require("ws");

if (!process.env.NLF_API_KEY) {
  throw new Error("Set NLF_API_KEY before starting the client.");
}

const ws = new WebSocket(
  "wss://ws.newlistings.pro/v2/full?exchange=robinhood&market_type=spot",
  { headers: {
    authorization: `Bearer ${process.env.NLF_API_KEY}`
  } }
);

ws.on("message", raw => {
  const message = JSON.parse(raw.toString());
  if (message.type === "error") {
    console.error(message.code, message.message);
    return;
  }
  const classification = message.parser?.classification;
  if (classification?.event !== "listing") return;

  for (const asset of message.parser.assets) {
    console.log({
      id: message.id,
      symbol: asset.symbol,
      type: classification.type,
      display: message.parser.display,
      url: message.url,
      contracts: asset.contracts,
      suggested_contracts: asset.suggested_match?.suggested_contracts
    });
  }
});

ws.on("error", error => console.error(error.message));

Connection examples and regional hosts

Fields to use in your client

On /v2/full, loop through parser.assets because a notice can name several tokens. contracts contains source-confirmed addresses when available. suggested_match.suggested_contracts contains candidate addresses, with confidence under suggested_match.confidence. Read the chain and address together; the recorded Robinhood Chain examples use chain: robinhood.

Route assets to the rules you use for asset discovery and spot to the rules you use for new tradable listings. Keep the classification alongside the symbol so a catalog addition does not trigger a rule intended for live spot trading.

parser.display is the readable summary, url points to the source, and detected_time_us and sent_time_us provide event timestamps at microsecond precision. Fast provides raw text, the exchange, source URL and timestamps without Full's classification or asset fields.

Keep reading

Get a free key