Skip to content

Coinbase listing WebSocket API for spot, roadmap and asset alerts

Coinbase spot listings, roadmap additions and asset-catalog discoveries reach your bot as separate events through the New Listings Feed WebSocket API. Low-latency delivery brings the announcement to your application; parsed tickers and classifications tell it what changed so it can apply the right rules.

Coinbase events we send

Coinbase spot listings, roadmap additions and asset discoveries use parser.exchange: coinbase. All three are listing events, so read parser.classification.type to tell them apart. Coinbase International perpetual-futures listings use the separate exchange identifier coinbaseinternational.

Scroll horizontally to compare all columns.

Coinbase coverage on /v2/full
Noticeexchangeevent / market_type
Spot listing announcementcoinbaselisting / spot
Listing-roadmap additioncoinbaselisting / roadmap
Asset-catalog discoverycoinbaselisting / assets
International perpetual-futures listingcoinbaseinternationallisting / futures
Spot or futures delistingcoinbasedelisting / spot or futures

A roadmap addition and a spot listing answer different questions

A roadmap alert tells your bot that Coinbase added a token to its listing roadmap. Coinbase describes the roadmap as assets it has decided to list, while stating that transfers and trading are unsupported until a listing is officially announced. Use the alert to identify the token, review its existing markets and prepare your listing rules.

A spot alert carries the spot-listing announcement. Read its source text for the planned trading date, pair and conditions. A spot announcement can precede the opening of trading: the BLUECHIP example below said its USD pair would open later that day if liquidity conditions were met.

An assets event is an asset-catalog discovery. It is a separate classification from a roadmap addition or spot announcement and does not confirm that trading has started. STARTER and PRO receive these events; FREE excludes assets.

Listing announcements and Coinbase market data

New Listings Feed gives bot builders a WebSocket feed with source links and parsed listing classifications across Coinbase and the other exchanges they follow.

A listing event and market data serve different jobs. The event identifies the announcement and its tokens; prices, order books and trading status describe the market where your system could act. Keep those inputs separate when evaluating an announcement.

Published Coinbase spot and roadmap examples

This recorded /v2/fast Coinbase event took 214µs (0.214ms) from detection to publication.

On 16 September 2026, the feed recorded BLUECHIP and RITUAL entering the Coinbase roadmap, followed by a separate BLUECHIP spot-listing announcement. These public records show why a client should retain both the ticker and the event type.

The Full JSON excerpts below are illustrative reconstructions from the linked records. Event IDs, timestamps, source text and enrichment are omitted.

  • /v2/fast · $BLUECHIP Coinbase spot announcement · 0.214ms processing
    v2 JSON example
    {
  "id": 3665047640694784,
  "type": "tweet",
  "exchange": "coinbase",
  "username": "CoinbaseMarkets",
  "text": "Spot trading for BLUE CHIP (BLUECHIP) will go live on 16 September 2026. The opening of our BLUECHIP-USD trading pair will begin later today if liquidity conditions are met, in regions where trading is supported.",
  "url": "https://x.com/CoinbaseMarkets/status/2100251877065527691",
  "detected_time_us": 1789574043308603,
  "sent_time_us": 1789574043308817
}
  • $BLUECHIP listed on Coinbase spot
    v2 JSON example
    {
  "type": "tweet",
  "username": "CoinbaseMarkets",
  "url": "https://x.com/CoinbaseMarkets/status/2100251877065527691",
  "parser": {
    "exchange": "coinbase",
    "classification": {
      "event": "listing",
      "type": "spot",
      "category": "crypto"
    },
    "display": "$BLUECHIP listed on Coinbase spot",
    "assets": [
      {
        "symbol": "BLUECHIP"
      }
    ]
  }
}
  • $BLUECHIP, $RITUAL added to Coinbase roadmap
    v2 JSON example
    {
  "type": "tweet",
  "username": "CoinbaseMarkets",
  "url": "https://x.com/CoinbaseMarkets/status/2100210481801707685",
  "parser": {
    "exchange": "coinbase",
    "classification": {
      "event": "listing",
      "type": "roadmap",
      "category": "crypto"
    },
    "display": "$BLUECHIP, $RITUAL added to Coinbase roadmap",
    "assets": [
      {
        "symbol": "BLUECHIP"
      },
      {
        "symbol": "RITUAL"
      }
    ]
  }
}

Filter Coinbase spot, roadmap or International listings

Set exchange=coinbase&market_type=spot,roadmap to receive both spot and roadmap events on Full. Comma-separated market types use OR. Different parameters combine with AND. Check parser.classification.event in your client to select listings and exclude delistings.

For Coinbase International perpetual futures, use exchange=coinbaseinternational&market_type=futures. Selecting only exchange=coinbase will exclude that separate feed.

To select posts from CoinbaseMarkets, use data_type=tweet&username=coinbasemarkets. Omit exchange if you want posts across both Coinbase identifiers. To receive raw events on Fast, use the exchange or username filter without market_type.

Node.js: receive Coinbase spot-listing events

Install ws, set NLF_API_KEY, and save this example as coinbase-listings.cjs. Run node coinbase-listings.cjs. It uses the FREE Full host, selects Coinbase spot events and logs every ticker in a listing notice.

For roadmap events, change the URL to market_type=roadmap and the client check to classification.type !== "roadmap". To receive both, use market_type=spot,roadmap and allow both types in the client check. STARTER and PRO keys use a regional host such as ny.newlistings.pro.

// 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=coinbase&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 parser = message.parser;
  const classification = parser?.classification;
  if (parser?.exchange !== "coinbase" ||
      classification?.event !== "listing" ||
      classification.type !== "spot") return;

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

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

Compare Coinbase listing arrivals from your bot server

For Coinbase, 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. Compare equivalent spot or roadmap announcements from your bot server.

FREE supports integration testing with a 3-second configured delay and no onchain enrichment. A comparison of PRO delivery requires a PRO capture with its zero configured delay. Network transit still takes time. Keep announcement arrival separate from the later time your venue accepts an order.

Keep reading

Get a free key