Onchain data with your listing alerts
New Listings Feed connects exchange announcements to onchain assets. Our paid WebSocket feed includes contract addresses, project matching, DEX pairs and market metrics when available, alongside listing and delisting events across 24 exchange feeds.
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.
| 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. |
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.
| 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.
| 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 futures listing or Alpha announcement before using the attached token data.
Scroll horizontally to compare all columns.
| Field | What your client can use it for |
|---|---|
content.title and url | Read the original announcement wording and open its source. Source content varies by event type and key. |
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 illustrative /v2/full excerpts use published NLF listings and contract data recorded in Tokyo. Event IDs, timestamps and market metrics are omitted. Dates are publication dates in UTC.
The 4STOCK Alpha event carries a confirmed BSC contract. The REZ event has an empty contracts array and a candidate under suggested_match, preserving the difference in the payload.
- $4STOCK live on Binance alpha
v2 JSON example
{ "type": "announcement", "url": "https://www.binance.com/en/binancewallet/0xd270d4e1ec6e6e0d28c0ecb8be966ec75997ffff", "content": { "title": "New Binance Alpha: 4Stock (4Stock). Chain: BSC. Contract: 0xd270d4e1ec6e6e0d28c0ecb8be966ec75997ffff. MC: 57724461" }, "parser": { "exchange": "binance", "classification": { "event": "listing", "type": "alpha", "category": "crypto" }, "display": "$4STOCK live on Binance alpha", "assets": [ { "symbol": "4STOCK", "contracts": [ { "chain": "bsc", "contract": "0xd270d4e1ec6e6e0d28c0ecb8be966ec75997ffff" } ] } ] } } - $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" } ] } } ] } }
Fast announcements, with the data your system needs
/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 in Unix epoch microseconds, so you can measure the delivery of the event your system actually uses.
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 includes parsed events with a 3-second configured delay, without contracts, suggested matches or metrics. Use a free key to inspect event classification and delivery; use a paid key for onchain enrichment.