Onchain data for crypto listing and sniping bots

New Listings Feed pairs low-latency WebSocket events with token contracts, project matches, DEX pairs and market metrics when available on paid keys. These fields help your bot identify the asset behind an announcement. Confirmed contracts and inferred matches are labeled separately.

Identify the token onchain

A ticker tells your bot which symbol was announced. A chain and contract address identify the asset to look up onchain. In /v2/full, each asset sits under parser.assets, with its own identity and enrichment.

When an exchange publishes a contract address, we place it in contracts. Confirmed describes the address supplied by the source; it is not a token audit. Optional fields are omitted when the data is unavailable.

Scroll horizontally to compare all columns.

Asset identity fields in parser.assets
Field	What it gives your system
`symbol` and `name`	The detected ticker and, when available, project name. Use them for labels and matching against your existing asset records.
`contracts[].chain`	The network for the address. Select the corresponding network client or token lookup.
`contracts[].contract`	The token address on that chain. Use the chain and address together to identify the token, rather than relying on a symbol that other assets may share.

Read the Full payload schema

Resolve a project when the notice has no address

When contracts is empty, our matcher may attach suggested_match. This gives your system a candidate project and addresses to evaluate when the announcement only names a ticker.

project_name names the candidate. confidence is labeled medium, high or very high, so your consumer can apply different handling to each level. These are confidence labels, not numerical probabilities or confirmation by the exchange.

suggested_contracts contains candidate chain and contract pairs. Each entry has those two fields only. The candidate may be wrong, and its chains do not establish where the exchange supports deposits or withdrawals. If no match is available, the event can have an empty contracts array without suggested_match.

Find DEX pools and assess their liquidity

Confirmed contract entries can include dex_pairs. These fields connect the token to a DEX pool and give your system liquidity and trading-activity context for its own quote checks.

Scroll horizontally to compare all columns.

Optional DEX pair fields under contracts[].dex_pairs
Field	Why it matters
`dex_id`	Identifies the DEX, so your integration can select the appropriate venue adapter.
`pair`	Names the trading pair and quote asset. Useful for display and matching the pool to your strategy.
`pair_contract`	Identifies the pool itself, separately from the token contract. Use it when checking that specific pool.
`volume_24h_usd`	The pool’s 24-hour trading volume in USD. Use it as an activity measure alongside liquidity.
`liquidity_usd`	The pool’s liquidity value in USD. Useful for screening pools before requesting a quote; it does not state the size you can trade at a given slippage.

Read market cap, FDV and supply together

metrics can appear directly on an asset or inside suggested_match. In the latter case, the numbers describe the candidate project and carry the same identity uncertainty.

Scroll horizontally to compare all columns.

Market and supply fields in metrics
Field	Why it matters
`circulating_market_cap_usd`	The USD value attributed to circulating supply. Use it to group assets by market size.
`fdv_usd`	Fully diluted valuation in USD. Compare it with circulating market cap to understand the difference between circulating and diluted valuation.
`circulating_supply`	The reported circulating token quantity. Adds supply context to market cap.
`total_supply`	The reported total token quantity. Compare it with circulating supply; it does not provide an unlock schedule.

Keep the original announcement with the asset

Onchain data arrives with the exchange event that triggered it. Your bot can distinguish a spot listing from a perps listing or Alpha announcement before using the attached token data.

Scroll horizontally to compare all columns.

Announcement context in /v2/full
Field	What your client can use it for
`content.title` and `url`	Read the original title when available and open the source URL. Use parser.display for the parsed summary; content.title is optional.
`parser.exchange`	Identify the exchange behind the event.
`parser.classification.event` and `parser.classification.type`	Select listings or delistings, then the relevant market or product type. Unclassified notices use event none.
`parser.classification.markets`	When available on an Upbit spot listing, identify quote markets such as krw or usdt. These are exchange trading pairs, not blockchain networks.
`parser.display`	A readable parsed summary for logs or interfaces, when available.

Confirmed contracts and suggested matches in real listings

These /v2/full examples use published New Listings Feed listings and recorded payloads. The 4STOCK example is shown in full, including the recorded event ID, timestamps, metrics and every returned DEX pair. Its values are the snapshot sent with that event, not current market data. Dates are publication dates in UTC.

The 4STOCK Alpha Live event carries a confirmed BSC contract, market metrics and three returned PancakeSwap pools with their recorded 24-hour volume and liquidity. The REZ event has an empty contracts array and a candidate under suggested_match, preserving the difference in the payload.

Sep 9, 2026$4STOCK live on Binance alpha

v2 JSON example

{
  "id": 3663768224606208,
  "type": "announcement",
  "url": "https://www.binance.com/en/binancewallet/0xd270d4e1ec6e6e0d28c0ecb8be966ec75997ffff",
  "content": {
    "title": "New Binance Alpha: 4Stock (4Stock). Chain: BSC. Contract: 0xd270d4e1ec6e6e0d28c0ecb8be966ec75997ffff. MC: 57724461"
  },
  "parser": {
    "assets": [
      {
        "name": "4Stock",
        "symbol": "4STOCK",
        "metrics": {
          "fdv_usd": 42000000,
          "total_supply": 1000000000,
          "circulating_supply": 1000000000,
          "circulating_market_cap_usd": 42000000
        },
        "contracts": [
          {
            "chain": "bsc",
            "contract": "0xd270d4e1ec6e6e0d28c0ecb8be966ec75997ffff",
            "dex_pairs": [
              {
                "pair": "4stock/usdt",
                "dex_id": "pancakeswap-v3-bsc",
                "liquidity_usd": 1000000,
                "pair_contract": "0x90c3c770087eb9e63ad47e99a66e260aa10c31ae",
                "volume_24h_usd": 60000000
              },
              {
                "pair": "4stock/usdt",
                "dex_id": "pancakeswap",
                "liquidity_usd": 1000000,
                "pair_contract": "0x90c3c770087eB9e63ad47E99a66e260aA10c31Ae",
                "volume_24h_usd": 48000000
              },
              {
                "pair": "4stock/usdt",
                "dex_id": "pancakeswap",
                "liquidity_usd": 250000,
                "pair_contract": "0x2Fe13112be502026671A6E76aF45d14eC394022D",
                "volume_24h_usd": 31000000
              }
            ]
          }
        ]
      }
    ],
    "display": "$4STOCK live on Binance alpha",
    "exchange": "binance",
    "classification": {
      "type": "alpha-live",
      "event": "listing",
      "category": "crypto"
    }
  },
  "detected_time_us": 1788949328421097,
  "sent_time_us": 1788949328452671
}

Sep 10, 2026$REZ listed on Upbit spot

v2 JSON example

{
  "type": "announcement",
  "url": "https://upbit.com/service_center/notice?id=26668186",
  "content": {
    "title": "렌조(REZ) 신규 거래지원 안내 (USDT 마켓)"
  },
  "parser": {
    "exchange": "upbit",
    "classification": {
      "event": "listing",
      "type": "spot",
      "category": "crypto",
      "markets": [
        "usdt"
      ]
    },
    "display": "$REZ listed on Upbit spot",
    "assets": [
      {
        "symbol": "REZ",
        "contracts": [],
        "suggested_match": {
          "confidence": "high",
          "project_name": "Renzo",
          "suggested_contracts": [
            {
              "chain": "ethereum",
              "contract": "0x3b50805453023a91a8bf641e279401a0b23fa6f9"
            }
          ]
        }
      }
    ]
  }
}

Test the fastest listing feed with the data your bot needs

New Listings Feed is the fastest crypto listing WebSocket for bots and listing snipers. Test it with the event your bot uses. /v2/fast sends the raw notice before parsing; /v2/full follows with the parsed event and available enrichment. Both include detected_time_us and sent_time_us. If your listing sniper needs a contract address, measure the full event's arrival.

Onchain and market values arrive with the announcement. They are not a continuous price feed or an executable quote. The documented /v2/full payload has no token-price field; obtain a current quote through your own market-data or trading connection.

STARTER and PRO include the same onchain fields when available. FREE provides parsed events at wss://ws.newlistings.pro/v2/full with a 3-second configured delay, without contracts, suggested matches or metrics. Test classification with FREE; use PRO to test enriched delivery with zero configured delay. Judge the payload and arrival time from your own server.

Keep reading

Get a free key