Manage smart alerts — list, create, update, toggle, delete. Use when setting up or managing token flow alerts, smart money alerts, or notification rules.

Smart Alerts CRUD management for smart alerts. Alerts are internal only (requires Nansen internal API key). Quick Reference Options Reference Flag Create Update Toggle Delete <id (positional) required required required name required optional type required required with type specific flags chains recommended optional telegram chat ID optional slack webhook URL optional discord webhook URL optional webhook endpoint URL optional optional webhook secret optional (webhook only) optional description optional optional enabled flag flag disabled flag flag flag data optional (JSON escape hatch) optional Alert Types 1. sm token flows — Smart Money Token Flows Track aggregated SM inflow/outflow. At least one flow threshold should be specified. Type specific flags: inflow 1h min/max , inflow 1d min/max , inflow 7d min/max (USD thresholds) outflow 1h min/max , outflow 1d min/max , outflow 7d min/max netflow 1h min/max , netflow 1d min/max , netflow 7d min/max token <address:chain (repeatable) — include specific tokens exclude token <address:chain (repeatable) token sector <name / exclude token sector <name (repeatable) token age max <days market cap min/max <usd , fdv min/max <usd Example: 2. common token transfer — Token Transfer Events Track real time transfer events matching specified criteria. Subject types: address , entity , label , custom label Format: subject type:value (e.g. subject label:"Centralized Exchange" ) Type specific flags: events <buy,sell,swap,send,receive (comma separated) usd min/max <usd , token amount min/max <n subject <type:value (repeatable) — addresses/entities/labels to track counterparty <type:value (repeatable) — requires subject token <address:chain / exclude token <address:chain (repeatable) token sector <name / exclude token sector <name (repeatable) token age min/max <days , market cap min/max <usd exclude from <type:value / exclude to <type:value (repeatable) Event direction notes: buy for counterparties = sell for subjects send for counterparties = receive for subjects To track "any address sending to CEX": use subject with receive , not counterparty with send Example: 3. smart contract call — Smart Contract Interactions Track contract calls matching specified criteria. Type specific flags: usd min/max <usd signature hash <hash (repeatable, e.g. 0x095ea7b3 for approve ) caller <type:value / exclude caller <type:value (repeatable) contract <type:value / exclude contract <type:value (repeatable) Example: Notes Chain aliases: Hyperliquid = hyperevm , BSC = bnb . Multiple channels can be combined: telegram 123 slack https://... webhook https://... webhook <url sends a POST request with the alert payload to any HTTP/HTTPS endpoint. Useful for server deployments, Zapier, n8n, or custom integrations. The endpoint must be publicly reachable and return a 2xx response. data '<json ' merges raw JSON on top of named flags (escape hatch for fields without named flags). Alert endpoints are internal only. Non internal users receive 404. Use single quotes for names with $ or special characters: name 'SM $1M'

nansen-smart-alerts