Telegram Alerts
The same listing, delisting, and risk events that stream over the WebSocket API are also pushed to a public Telegram channel. Telegram is for humans watching a phone; the WebSocket API is for bots reacting programmatically. Most users pick one; some run both — Telegram to keep an eye on the market, the API to act on it.
The channel
| Channel | Handle | Join |
|---|---|---|
| Main feed | @CLWfeed | t.me/CLWfeed |
Open the link in any Telegram client and tap Join. No API key is required to read
the channel. @CLWfeed is also where keys, rotations, expiry extensions, and tier
changes are handled — see Authentication.
@CLWfeed is the only official channel. There is no clwebsocket or
cryptolistingwebsocket channel — treat any other handle as impersonation.
WebSocket vs Telegram
Both surfaces carry the same events. They differ in form and in who consumes them.
| Aspect | WebSocket API | Telegram (@CLWfeed) |
|---|---|---|
| Consumer | A program (trading bot, script) | A person reading notifications |
| Format | Structured JSON, machine-parseable | Human-readable text message |
| Delivery | Direct push over your own WSS connection | Telegram’s push-notification network |
| Timing | Real-time, as soon as an event is detected | Adds Telegram’s own notification delivery time on top |
Pre-parsed ticker | Yes — a field your code branches on | Shown in the text, but you read it, you don’t parse it |
| Filtering | Per-exchange via ?cex=, per-type in your handler | You see the whole feed and skim |
| Microsecond timestamps | Yes (detectedTimestampUs, dispatchTimestampUs) | Not included |
| Automation | Built for it | Not suitable — a human is in the loop |
| API key | Required | Not required to read the channel |
The practical takeaway: if a machine needs to act on an event, use the WebSocket API. Telegram’s push layer sits between the event and your phone, and a human tapping a notification is never going to be as fast as code already holding an open socket. Use Telegram to stay informed, not to trade on.
What a Telegram subscriber receives
A channel post for each event, in plain language — the exchange, the ticker, and the event type (new listing, delisting, monitoring-tag change, caution released, and so on). It is a readable notification you can glance at.
What Telegram does not give you
- No JSON. Nothing to
json.loads(); the message is prose, not a payload. - No timestamps. The microsecond
detectedTimestampUs/dispatchTimestampUsfields (see Message Reference) exist only on the API. - No per-connection filtering. There is no
?cex=on a channel — every subscriber sees the same posts. Filtering by exchange or event type is an API feature. - No programmatic guarantees. Rate limits, reconnection semantics, and close codes (Error Handling) apply to the WebSocket, not to a chat channel.
- Not built for latency-sensitive automation. The notification path adds Telegram’s own delivery time, and it is meant to be read, not consumed by a bot.
Do not build a trading bot on top of the Telegram channel by scraping messages. It is slower than the API, carries no structured fields, and offers none of the delivery guarantees your code needs. Use the WebSocket API for anything automated.
Next steps
| Page | Purpose |
|---|---|
| Quick Start | Connect to the WebSocket API in minutes |
| Authentication | Request a key on @CLWfeed |
| Exchange Filtering | Narrow the API stream by exchange and type |
| Message Reference | JSON schema Telegram posts don’t carry |