Filters and coverage

Set filters in the connection URL. They are fixed when you connect. Different parameters use AND. exchange, data_type, market_type, and category accept comma-separated values with OR; username accepts one handle.

Exchange, data-type, market-type, and category values are trimmed and case-insensitive, and each one matches in full. For example, market_type=alpha does not include alpha-live. List every value you want. Both endpoints accept up to 32 exchanges. The query is limited to 1,024 bytes, and each exchange value and the username to 64 bytes.

Exchange coverage

Listings, Delistings and Cautions show Full's parsed market types. Read parser.classification.event to distinguish them. Fast has no market-type classification.

Binance Alpha statuses

Alpha Featured and Alpha Live are separate notices. A feature notice can arrive days before trading opens:

Both use parser.classification.event: "listing". An Alpha Live notice for the same token can arrive before or after the feature notice.

Every alpha-live asset carries is_scheduled. It is true when the token is listed on Alpha 2.0 through a scheduled, previously announced event (such as a Binance Wallet TGE, airdrop, etc), and false for a fresh, surprise listing.

To receive both on Full, use exchange=binance&market_type=alpha,alpha-live. Use either market type alone to select one notice type.

{
  "id": 3667436619893557,
  "type": "tweet",
  "username": "BinanceWallet",
  "url": "https://x.com/BinanceWallet/status/2105144506882625697",
  "content": {
    "text": "Binance Alpha will be the first platform to feature Concrete (CT) on September 30. Eligible users can claim their airdrop using Binance Alpha Points on the Alpha Events page once trading opens. Further details will be announced soon. Please stay tuned to Binance’s official…"
  },
  "parser": {
    "exchange": "binance",
    "classification": {
      "event": "listing",
      "type": "alpha",
      "category": "crypto"
    },
    "display": "$CT featured on Binance Alpha",
    "assets": [
      {
        "symbol": "CT",
        "name": "Concrete",
        "contracts": []
      }
    ]
  },
  "detected_time_us": 1790740537130953,
  "sent_time_us": 1790740537135732
}

{
  "id": 3667466661975727,
  "type": "announcement",
  "url": "https://www.binance.com/en/binancewallet/0x0a092e544da31150b439a1aaa1a3a2214a867f46",
  "parser": {
    "exchange": "binance",
    "classification": {
      "event": "listing",
      "type": "alpha-live",
      "category": "crypto"
    },
    "display": "$CT live on Binance Alpha 2.0",
    "assets": [
      {
        "symbol": "CT",
        "name": "Concrete",
        "is_scheduled": true,
        "contracts": [
          {
            "chain": "bsc",
            "contract": "0x0a092e544da31150b439a1aaa1a3a2214a867f46"
          }
        ],
        "metrics": {
          "circulating_market_cap_usd": 52887425,
          "total_supply": 1000000000
        }
      }
    ]
  },
  "detected_time_us": 1790755206042043,
  "sent_time_us": 1790755206044160
}

Caution notices

Upbit, Bithumb and Binance flag risky assets with caution notices. Each caution event carries the affected assets and one action:

All four use parser.classification.event: "caution" and category: "crypto". A notice that designates some assets and lifts others sends one event per action, both with the same url.

To receive only cautions on Full or in history, use market_type=designated,extended,lifted,warning.

{
  "id": 3667883215489431,
  "type": "announcement",
  "url": "https://upbit.com/service_center/notice?id=1451240977",
  "content": {
    "title": "블라스트(BLAST) 거래 유의 종목 지정 안내"
  },
  "parser": {
    "exchange": "upbit",
    "classification": {
      "event": "caution",
      "type": "designated",
      "category": "crypto"
    },
    "display": "$BLAST designated for caution on Upbit spot",
    "assets": [
      {
        "symbol": "BLAST",
        "contracts": []
      }
    ]
  },
  "detected_time_us": 1790958601313993,
  "sent_time_us": 1790958601316191
}

Data types and usernames

data_type matches the top-level type field. Omit it to receive both announcements and posts.

A username filter selects posts only. It cannot be combined with data_type=announcement.

wss://tokyo.newlistings.pro/v2/full?data_type=tweet&username=BinanceWallet
wss://tokyo.newlistings.pro/v2/fast?data_type=tweet&username=BinanceWallet

Combine filters

Upbit spot announcements:

wss://tokyo.newlistings.pro/v2/full?exchange=upbit&data_type=announcement&market_type=spot

Each event must match all three filters. Use market_type=spot,futures to accept either market type. Unclassified events do not match a market-type filter.

Every connection also has a category. Without category, Full delivers crypto listings, delistings and cautions plus every event that carries no category, such as tweets and unclassified announcements. Add category=rwa for real-world-asset markets only, or category=crypto,rwa for both.

Unknown exchange, market-type, or username values match no events. Empty values, repeated parameters, unknown parameter names, invalid data types and contradictory filters return 400 INVALID_REQUEST; Full also rejects malformed percent escapes.