Watches
A watch is the core object in SCMon. It says: on this chain, for this token, on this address — when a transfer matches my rule, deliver it here.
Fields
| Field | Required | Description |
|---|---|---|
chain | yes | bsc or tron (Ethereum coming later). |
token | yes | Token contract address for the chain (lowercased), or native for the chain coin. |
address | yes | The wallet you want to watch. Matched case-insensitively. |
label | no | A human name shown in alerts and the dashboard. |
rule | no | Narrows which transfers fire — see Rules. Defaults to any transfer. |
channel_type | yes | webhook or telegram (slack, whatsapp coming soon). |
channel_target | yes | The webhook URL or Telegram chat id. |
Direction is automatic
You don’t tag the address as “incoming” or “outgoing” — SCMon derives direction from each transfer (whether your address is the recipient or the sender) and exposes it to your rule and to the payload as direction + counterparty.
Managing watches
| Method | Path | Notes |
|---|---|---|
POST | /v1/watches | Create a watch (201). Returns 402 if you’ve hit your plan’s watch limit. |
GET | /v1/watches | List your watches. |
GET | /v1/watches/:id | Fetch one. |
PATCH | /v1/watches/:id | Update label, rule, channel_type, channel_target, or active. |
DELETE | /v1/watches/:id | Remove it (204). |
Pause a watch without deleting it by setting active: false via PATCH.