On this page
Choose events that match the task
Launch and graduation signals help with discovery. Momentum and volume events describe observed trading changes. Wallet signals connect activity to followed addresses. Risk events can highlight a creator sale or liquidity problem. AI-pick and research events carry an opinion that should be checked against its sources.
A “buy call” is a recorded model or rule output, not a fill confirmation. Open the coin, verify the mint and inspect the event timestamp before using a notification to make a decision.
Configure local notification delivery
- Open Settings in your local installation and configure a supported Discord or Telegram destination.
- Choose the event types you want delivered.
- Use coin, wallet or type rules to mute noise, and set quiet periods or cooldowns where appropriate.
- Send the destination's test notification, then inspect delivery history.
- Check Health if alerts stop; the local service must remain running to observe events.
An event visible in the dashboard does not mean a message reached an external destination. Browser notifications also depend on browser permissions and whether the browser is running. Hosted notification access can differ from the local settings interface.
Build a read-only alert consumer
Developer examples below run against your BLIX account: sign in, open Developers and copy your session into BLIX_SESSION; every request sends it as the blix_wait cookie.
curl -s 'https://blixvip.com/api/signals?safety=passed&limit=20' -H 'cookie: blix_wait='$BLIX_SESSION
curl -N https://blixvip.com/api/stream -H 'cookie: blix_wait='$BLIX_SESSIONUse the event stream for incoming signals and the query endpoint for a recent snapshot. A safety filter narrows the available record; it does not eliminate token risk. Treat source outages and reconnects as possible gaps rather than silently claiming uninterrupted coverage.
About this guide
Reviewed by BLIX on October 10, 2026 against the product implementation. Availability depends on your account and connected providers. Explore the BLIX guides for related workflows.
Frequently asked questions
Will I receive alerts while my local PC is off?
No. A local service cannot observe or deliver events while its host is stopped. An always-running deployment needs its own configured destinations.
Does receiving a signal place an order?
No. Delivery and execution are separate flows.