veirox notify
Shared destinations, admin routing, your personal notification schedule, the inbox, and delivery logs
Synopsis
veirox notify <subcommand> [args] [flags]
Description
Every notification always lands in your in-app inbox, no matter what's
configured below — that's the always-on system of record. destination and route are
admin surfaces for org-wide Slack/Telegram/WhatsApp/Pushover channels; prefs and inbox
are yours, personally.
Subcommands
| Command | Description |
|---|---|
veirox notify destination | Admin: manage shared Slack/Telegram/WhatsApp/Pushover destinations |
veirox notify route | Admin: route events to shared destinations by event/category/severity |
veirox notify prefs | Your personal channel matrix, mute, quiet hours, digest, and snooze |
veirox notify inbox | Read your in-app notification inbox + per-notification delivery status |
veirox notify logs | List notification delivery logs |
veirox notify send <channel-id> | Send a one-off notification |
veirox notify destination
Admin CRUD over shared, org- or project-scoped Slack/Telegram/WhatsApp/Pushover destinations. Secrets (webhook URLs, tokens) are write-only — reads always return a redacted config.
| Command | Description |
|---|---|
notify destination list | List destinations |
notify destination create | Create a destination — --kind, --name, --config-json |
notify destination rm <id> | Delete a destination |
veirox notify destination create --kind slack --name '#ops-alerts' \
--config-json '{"webhook_url":"https://hooks.slack.com/services/..."}'
veirox notify route
Admin routing rules — which shared destinations receive an event, filtered by event type and/or category with a minimum severity floor. Fires once per event, never per recipient.
| Command | Description |
|---|---|
notify route list | List routing rules |
notify route create | Create a rule — --name, --destinations (required), plus --category, --min-severity |
notify route rm <id> | Delete a rule |
veirox notify prefs
Your personal notification schedule — none of it touches the in-app inbox, which is always immediate. Only external personal channels (email, web push) are affected.
| Command | Description |
|---|---|
notify prefs show | Show your category matrix and schedule |
notify prefs set | Set personal channels for a category — --category, --channels |
notify prefs mute / unmute | Mute/unmute a category's external channels — --category |
notify prefs quiet-hours set / clear | Daily hold-off window — --start, --end, --tz |
notify prefs digest | Batch delivery cadence — --cadence instant|hourly|daily |
notify prefs snooze / unsnooze | Pause everything external for a while — --for 8h |
veirox notify prefs set --category security --channels email,web_push veirox notify prefs quiet-hours set --start 22:00 --end 07:00 --tz UTC veirox notify prefs snooze --for 8h
veirox notify inbox
The in-app inbox — the system of record. Every user-facing event lands here, always, regardless of external channel configuration.
| Command | Description |
|---|---|
notify inbox list | List notifications — --unread, --category |
notify inbox read <id> / read-all | Mark one or all notifications read |
notify inbox unread-count | Show the unread count |
notify inbox deliveries <id> | Per-channel delivery status for one notification |
veirox notify logs
List notification delivery logs
veirox notify logs
veirox notify send <channel-id>
Send a one-off notification
| Flag | Type | Default | Description |
|---|---|---|---|
--message | string | — | message body |
veirox notify send <uuid> --message 'hello from CI'
Exit codes
| Code | Meaning |
|---|---|
0 | Success. |
1 | Generic error (network, API 5xx). |
2 | Validation error (bad flag, missing required arg). |
3 | Unauthenticated — run veirox login or set VEIROX_API_KEY. |
4 | Not found (resource does not exist in this project). |
5 | Permission denied (your role / API key lacks the scope). |