Connection and Channels

Endpoints, authentication, channels, and tier-based access.

Endpoints #

Two regional endpoints share the same API key:

If you trade on Binance, Gate.io or another Tokyo-based exchange — use Tokyo. Otherwise — Seoul for Upbit and Tokyo for the rest.

Authentication #

Append your license key as a key= query parameter on the connection URL:

wss://<endpoint>/<channel>?key=YOUR_API_KEY

The same key works on both endpoints.

Channels #

Both endpoints expose the same two channels:

Which one to pick #

/listings is the managed stream. We curate it down to listing-class events — new spot and futures listings, delistings, launchpool, launchpad, megadrop, pre-market launches, KRW and BTC market additions, caution flags, and deposit or withdrawal suspensions — and add a coins array with extracted ticker symbols. Best for clients who want a ready-to-use signal.

/feed is the raw stream. Every announcement we receive flows through unchanged, including non-listing items such as maintenance windows, regulatory notices, exchange events, and deposit pauses outside our taxonomy. No coins field. No curation. Best for clients who want full coverage and their own filtering.

Filtering on /listings is keyword-based. If an exchange changes its announcement format we may miss some events until rules are updated. Choose /feed if that risk matters to you. See Filtering Guide for the keyword rules we apply.

Tier-based access #

The license tier controls server-side broadcast behavior. Delay applies equally to /feed and /listings — it's per-connection, not per-channel. See Tiers for the full matrix.

A Trial client connecting to /feed is closed at handshake-time with 1008 — Trial is /listings-only.

The first message after a successful handshake (the connection payload) reports tier and delay_ms. See Messages → connection confirmation.