Get a watch run summary
Returns one run in full: its counts, its per-stage activity log, and every delivery attempt with
the records it carried under notifications[].payload.notifications[]. That is the same record
shape your channel receives, so a watch is readable here even when no channel is configured.
Records are returned only for a run whose status is SUCCESS. A run can leave rows behind
without ever paying for or delivering them, and those rows must not be readable. The run itself,
with its status, counts, and logs, is still returned so you can see what happened.
Authorizations
API key passed as a Bearer token in the Authorization header.
Headers
API version to use. 2025-11-01 is the only accepted value. Send it on every call: it is
enforced today on POST /watch/{dataset}/search, where a missing or unrecognized value returns
400, and the other watch routes accept a request without it rather than relying on that.
2025-11-01 "2025-11-01"
Path Parameters
The dataset the watch is built on.
person, company, job "person"
The watch's id, returned when it was created.
46936
The run's id, from runs[].id on the run-history endpoint.
54811
Response
The run, its logs, and its deliveries.
One run in full, with its counts, its activity log, and its deliveries.
64200
"2026-07-16T03:19:00Z"
"2026-07-16T03:20:00Z"
RUNNING, SUCCESS, FAILED, SKIPPED "SUCCESS"
null
Records the run's query matched before any filtering.
1204
Records left after filtering, before the new-record check.
12
Records this run delivered.
1
5
The run's per-stage activity log.
Every delivery this run attempted, with the records it carried. Empty unless status is
SUCCESS: a run can leave rows behind without ever paying for or delivering them, and
those rows are not readable here.
Related topics
Get an entity watchGet a discovery watchList watch runsTest a discovery watchTest an entity watch
