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 monitor
Once your reference job completes withstatus: job_completed, use job_id to
create a monitor:
Webhooks are configured separately and attached via
webhook_ids. For
instructions, see Set up webhooks.Retrieve results
Use these endpoints to list monitors, inspect execution history, and pull aggregated records.List monitors
Get all monitors for your API key:List monitor jobs
Get execution history for a specific monitor:Get aggregated results
Retrieve all deduplicated records from all 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 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 monitors
Use these endpoints to update webhook assignments, pause, resume, or delete a monitor, and inspect its execution history.Update monitor
Update webhook assignments or the record limit for an existing 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 monitor.

