Test an entity watch
Pushes one sample notification through a saved entity watch so you can verify a receiver end to end: signature check, JSON parsing, routing, without waiting for a subject to actually move.
The envelope is exactly what a real run sends, flagged with metadata.test: true. The record
is built from the dataset’s own enrich model and filled with a fixed, public demo profile, so
your parser sees production structure without real subject data. The signature is computed the
same way as a real delivery, HMAC-SHA256 over <timestamp>.<raw-body> keyed by your API key,
sent as x-crustdata-signature: t=<unix>,v1=<hex>.
It runs no diff, records no snapshot, costs no credits, and persists nothing. All body fields are optional.
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. Entity watches support person and company; there is no
job entity watch, and job returns 404 here. Use /watch/job/search for jobs.
person, company "person"
The watch's id, returned when it was created.
46936
Body
Options for an entity watch's test send. Every field is optional.
Deliver this one test to a public URL you control instead of the watch's configured channels.
"https://your-server.example.com/webhook"
Project the sample record to a chosen field set for this test. Defaults to the watch's own fields, and is entitlement-checked like a create.
Deliver this many sample subjects in one envelope. Each gets a distinct record id.
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
Company Entity WatcherPerson Entity WatcherTest a discovery watchUpdate an entity watchList entity watches
