watch_event
Watch Event
Changes something you own.
Use this to star one event and arm alerts on it. Use update_watch instead for an event already watched, and create_view for alerts on every event that matches a screen. Add an event to the watchlist and start alerting on it. Alerts are ON by default (unusual price moves, on-sale, presale, event week, low inventory) and go to the same destinations as your other alerts. Triggers: price_z (unusual price move, on by default); pct_move (price % move); absorption (tickets leaving fast): Measures listings that disappear, which is not the same as confirmed sales.; demand (demand spike): A day-over-day change in Interest, not a z-score. Coverage is still filling in, so quiet events may never trigger it.; lifecycle (on-sale, presale, event week, low inventory, on by default). You may watch as many events as you like, but a plan may keep only its newest N of them alerting: check alerts_live on the result, and REPORT dormanted if it is non-empty: those events are still starred and have stopped alerting because this one took the slot. Starring an event that is already watched returns the existing watch unchanged; it never resets triggers you configured. A threshold outside its range is refused, never clamped: the error names the field and its min and max, and nothing is starred.
Parameters
| Name | Type | Required | Default | Notes |
|---|---|---|---|---|
event_id | string | yes | Event to watch (from search_events or screen_events). | |
triggers | object | Per-event trigger overrides, e.g. {"price_z":{"enabled":true,"params":{"threshold":2.5}}}. Omit to use your saved defaults. A value outside its range in list_watch_triggers is refused with an error naming the field and its min and max, and nothing is written. | ||
notification_mode | string | instant = email each alert as it happens (default); digest = the alerts go out together in one daily email; muted = record alerts without sending them. One of instant, digest, muted. |