wss://tokyo.newlistings.pro/v1/new-listings-enhanced
wss://tokyo.newlistings.pro/v1/delistings-enhanced
new-listings-enhanced and delistings-enhanced emit the same base payload as the standard channels, with additional fields on each detection: project name, market metrics, and onchain contracts with their DEX pairs. Coverage is identical to the standard variants.
Source contracts identify an authoritative match. Without one, the matcher may provide a suggested project match. Legacy v1 can also recommend an additional liquidity contract for an already identified project.
Authoritative contract
The contract published in the announcement stays under contracts. When the matcher resolves a project from that exact address, the project match is authoritative. Its available project_name and metrics appear directly on the detection. An unresolved source contract remains present even when project enrichment is unavailable.
Example of a PRO listing event with authoritative enrichment:
{
"time": 1787462404214,
"time_iso": "2026-08-23T05:20:04.214Z",
"delay": "0ms",
"id": 3660723003830272,
"announcement": "$QENIS listed on MEXC spot",
"original_title": "First in Market: QENIS Now Live on MEXC Meme+",
"url": "https://www.mexc.com/announcements/article/first-in-market-17827791537791",
"exchange": "mexc",
"type": "spot",
"detections": [
{
"ticker": "QENIS",
"project_name": "Qenis",
"metrics": {
"volume_24h_usd": 1300000,
"circulating_market_cap_usd": 3800000,
"fdv_usd": 3800000,
"circulating_supply": 963996857,
"total_supply": 963996857
},
"contracts": [
{
"contract": "EkcTa8n14fXcHdfvZqCg72cTCutJnnKb19vcHwKTpump",
"chain": "solana",
"dex_pairs": [
{
"dex_id": "pumpswap",
"pair": "qenis/sol",
"pair_contract": "HttDe6BsDc3y58owhqayQmERsNmWnRzFvDEwJYmxGAx3",
"volume_24h_usd": 950000,
"liquidity_usd": 220000
}
]
}
]
}
]
}
Suggested match
When the contract is not in the announcement, the matcher attaches a suggested_match describing its best guess for the ticker. Example detection with a suggested match:
{
"ticker": "DGAI",
"suggested_match": {
"confidence": "high",
"project_name": "DGrid AI",
"metrics": {
"volume_24h_usd": 110000000,
"circulating_market_cap_usd": 97000000,
"fdv_usd": 650000000,
"circulating_supply": 150000000,
"total_supply": 1000000000
},
"suggested_contracts": [
{
"chain": "bsc",
"contract": "0x10d4183389e99233db3cc981c43443ebd28ebd5e",
"dex_pairs": [
{
"dex_id": "pancakeswap-v3-bsc",
"pair": "dgai/usdt",
"pair_contract": "0x0e6e1f47c64f517fc9dc35698718c7dfc708d534",
"volume_24h_usd": 9200000,
"liquidity_usd": 2500000
}
]
}
]
}
}
For a candidate project, confidence describes the strength of the match: medium, high, or very high. A candidate does not establish which contract the exchange supports.
Additional liquidity contract
An authoritative contract and suggested_match can coexist in legacy v1. If another contract belonging to the same project has greater verified liquidity, the matcher can include it under suggested_match.suggested_contracts. The comparison requires complete liquidity observations for both contracts. The source contract stays in contracts, and the project identity remains authoritative.
In this case, suggested_match recommends a different contract for liquidity. It does not make the original project match uncertain or establish exchange deposit or withdrawal support for the additional contract. Liquidity is based on reported DEX pool reserves; it does not predict the price impact of an order.
This coexistence applies to legacy v1. /v2/full omits suggested_match when confirmed contracts are present.
Full field tables for metrics, contracts, dex_pairs, chains, and common dex_id values live in Message schemas.