Test a discovery watch
Delivers a sample notification so you can verify a receiver end to end before waiting for a real run.
The sample is built from real current matches of the watch’s own filter, ignoring the
watermark and the already-seen set, and shaped through the same processor a real run uses, so
the payload is identical to production apart from metadata.test: true. Nothing is recorded:
no run, no seen-set advance, no credit, no persistence.
Every body field is optional. Send deliver: false to get the envelope back without any
outbound request. If the watch’s filter currently matches nothing there is nothing to sample,
and the call returns 400 with the envelope still attached.
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
Body
Options for a discovery watch's test send. Every field is optional, so an empty object is a valid body.
Deliver this one test to a URL you control instead of the watch's configured channels,
which pairs well with a request-inspection service. Must be a public http(s) URL:
endpoints resolving to private, loopback, or link-local addresses are rejected.
"https://your-server.example.com/webhook"
How many real current matches to include in the one envelope, so you can exercise multi-record handling.
1 <= x <= 253
Set false to build and return the envelope without sending anything.
true
Response
A delivery was attempted. Read delivered[].http_status for each channel's outcome.
The result of a test send, carrying what each channel answered and the exact envelope that was delivered.
One entry per channel the test was sent to. Empty when deliver was false.
The body POSTed to each webhook channel, and the same body a test send returns under envelope.
The two watch kinds shape results differently. A discovery watch keys results by membership
polarity, so records arrive under results.added, each one the raw dataset record. An entity
watch delivers a flat list, one object per fired subject, each with its own changes and
record.
Related topics
Test an entity watchGet a discovery watchUpdate a discovery watchList discovery watchesCancel a discovery watch
