Create or update an ICP signal watch
Watch an ICP, so signals are detected on any company matching it — not only on companies already in your Key Accounts.
Keyed on the ICP, so there is at most one watch per ICP and calling this repeatedly is safe: it creates the watch the first time and reconfigures it afterwards.
Rejected with 422 when the ICP has no criteria, since that would match every company on the market.
Authorizations
Account API key passed in the Authorization header
Path Parameters
ICP criteria UUID. Create one via Create an ICP criteria.
Query Parameters
Target account UUID. Required for staff; ignored for customer keys.
Body
Signal types to detect. Supported: news, job_posting.
Defaults to true. Set false to record events without delivering them.
true
Which news topics to search. Supported: m_and_a, rebranding, funding_round, product_launch, relocation. Omit or send an empty array for every topic. Narrowing costs nothing and searches each selected topic more deeply, since a run's article budget is split across (markets x topics). Ignored when signal_types does not include news.
Response
OK
When the watch was first created.
The ICP whose matching companies are watched.
Watch UUID. Stable across reconfigurations; every endpoint keys on icp_criteria_id instead, so you rarely need this.
When false the watch keeps detecting and recording events but delivers nothing — useful to inspect what an ICP would produce before acting on it.
News topics this watch searches. Empty means every supported topic.
Signal types this watch produces.
When the watch was last reconfigured.