Update an alert
Partially update an alert. Provided fields replace existing values; entity lists, when provided, replace the full set.
Authorizations
Pass your API key in the X-API-Key header (recommended).
Path Parameters
Alert ID
Body
REALTIME, DAILY, WEEKLY 20001 - 100 elementsReplace the alert's filter set wholesale. Omit to leave the existing filters unchanged; send an empty object {} to clear all filters.
Toggle whether the alert produces matches. False pauses; true resumes.
1 - 20 elements1 - 200Response
OK
How often matches are delivered: REALTIME (a separate email per match), DAILY (one bundled email each morning at 13:00 UTC), or WEEKLY (one bundled email Monday 13:00 UTC). Defaults to REALTIME.
Whether the alert produces matches. Disabled alerts retain history but accumulate no new matches until re-enabled.
What signal the alert watches for. ENTITY_MENTION fires whenever a watched entity is mentioned in a podcast episode. PODCAST_SPEAKER fires only when a watched entity is themself an identified speaker on the episode, in one of the canonical appearance buckets — GUEST, PANELIST, CORRESPONDENT, or AUDIENCE (this last bucket absorbs callers, listeners, and other audience-side roles after server-side canonicalization). HOST is intentionally excluded — hosting the show isn't an appearance. Kind is fixed at creation.
ENTITY_MENTION, PODCAST_SPEAKER User who created the alert. Null when the alert was created via an API key.
Persistent narrowing applied to every surface the alert produces: the matches list, the realtime email, and the daily/weekly digest. Absent = no filters (every detected match is surfaced).