How it works
Each scheduled execution does the following:- Creates a new job with its own
job_id. - Uses a rolling date window based on schedule frequency.
- Applies the reference job’s validators, extractors, and schema.
- Deduplicates records across all runs and merges the results.
Before you begin
Create a successful job following the Quickstart guide.Create event monitor
Once your reference job completes withstatus: job_completed, use job_id to
create an event monitor:
Webhooks are configured separately and attached via
webhook_ids. For
instructions, see Set up webhooks.Retrieve results
Use these endpoints to list event monitors, inspect execution history, and pull aggregated records.List event monitors
Get all event monitors for your API key:List event monitor jobs
Get execution history for a specific event monitor:Get aggregated results
Retrieve all deduplicated records from all event monitor jobs:Export results as CSV
To download the most recent run’s records as a spreadsheet-friendly file, useGET /catchAll/monitors/pull/{monitor_id}/csv.
It returns the latest run as a text/csv download — one row per record, with
enrichment fields as columns and citations as a JSON column.
If the event monitor’s reference job used a connected entity dataset, connected
entities are split into event_associated_entities and mention_entities JSON
columns. When no entity dataset was used, those two columns are omitted from the
export entirely rather than included as empty columns — read columns by header
name so both shapes parse correctly.
Manage event monitors
Use these endpoints to update webhook assignments, pause, resume, or delete an event monitor, and inspect its execution history.Update event monitor
Update webhook assignments or the record limit for an existing event monitor. Pass a new list of webhook IDs to replace existing assignments. Pass an empty array to clear all assignments:Schedule and reference job cannot be modified. To change the query or schedule,
create a new event monitor.

