Setting up alerts

The channel comes first, and the screen is built that way

The first block on the Alerts screen is the delivery channel, and it carries the state of delivery: delivering, linked but muted, linked but pointing at another channel, or not linked at all. If nothing is linked, the block says in plain words that a qualifying trade will pass without reaching you.

Linking opens Telegram and connects your account in one step — no code to copy, no settings page to find. The link works once and expires after fifteen minutes, so if you get distracted, start it again rather than reusing the old one.

Linking and routing are two separate records, and the difference is the one that used to cost people their alerts. An account can hold a valid Telegram link while its delivery channel still points somewhere nothing is sent from. The block checks both before it turns green, and when only the routing is missing it says so and carries a button that changes the channel — nothing else has to be redone.

Note A screen that listed what you want to be told before saying where it would arrive would give the certainty that everything works. That is the failure this ordering exists to prevent.

What decides that an alert is sent

Two settings, and no others. The amount threshold sets the size below which a trade is not worth interrupting you for. The category filter narrows the stream to the market families you care about, and selecting none means every category rather than none.

The four presets fill the form rather than saving it: click one, adjust the threshold if you want, then save. A preset that saved on its own would overwrite a configuration you had spent time on, with one exploratory click.

Note Nothing else narrows the stream. There is no per-market condition and no per-address condition: an address on your Watchlist is a bookmark, and the Watchlist says so on its own screen rather than letting you assume otherwise.

The operators board is where most people find the wallets worth paying attention to in the first place, and it is the screen that tells you whether a record is a method or a streak.

The alert budget

Alerting has a budget, and the plans carry different ones — standard on Operator, raised on Principal. The pricing grid is where that line lives; no number appears in this guide, because a ceiling written into a guide is a number that drifts the day the ceiling moves.

The practical consequence: a threshold set far below what you would actually act on spends the budget on trades you were never going to trade. A narrow setting is not a courtesy to the service, it is how you keep the rare ones audible.

Webhooks and the API

Outbound webhooks and the REST API are sold on the Principal line of the pricing grid. The screen that will carry them is in the menu and states on the screen itself that it is announced and not yet delivered.

That is why this guide contains no endpoint, no signing scheme and no payload example. Earlier material described all three; documenting an integration nobody can configure is worse than naming the gap, because it is only discovered after payment.

What goes wrong, in order of frequency

• No channel linked. The trades qualify, nothing arrives, and the product looks broken while working exactly as configured.
• Linked but not routed. The link is valid and the delivery channel still points elsewhere; the block separates that case from the others rather than showing a single green tick.
• Channel linked but muted on the Telegram side. That is a third state, and it is named as one.
• A threshold so low that the stream fires continuously, which spends the budget and trains you to ignore the notification.
• Expecting delivery guarantees. Alerts are best-effort and depend on the channel staying reachable, and nothing in them is a recommendation to buy or sell.

Les questions auxquelles ce guide répond

Which delivery channels are available?

Telegram, and only Telegram today. The screen states this rather than listing channels that are planned.

I linked Telegram and nothing arrives. What now?

Read the delivery block at the top of the screen. Linking your account and routing alerts to it are two separate records, and the block checks both. If it says alerts are not routed to Telegram, the button in that block changes the channel and nothing else needs redoing.

My Telegram link expired. What do I do?

Start it again from the Alerts screen. The link is single-use and expires after fifteen minutes; nothing is broken and nothing needs unlinking first.

Can I alert on one specific market or one specific wallet?

Not today. Alerts are matched on trade size and category only, and the screen carries no setting that claims otherwise. When a narrower condition is served, this guide gains a section rather than a promise.

Can I send alerts to my own endpoint?

Not yet. Outbound webhooks are part of the Principal plan on the pricing grid, and the screen that will carry them says it is not delivered. When it ships, this guide gains a section rather than a promise.

Are alerts guaranteed to arrive on time?

No. They are best-effort and depend on the delivery channel staying reachable, and the screen says so where you configure them.