> ## Documentation Index > Fetch the complete documentation index at: https://docs.api.tamtam.ai/llms.txt > Use this file to discover all available pages before exploring further. # 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. ## OpenAPI ````yaml /reference/openapi.yaml put /v2/icp-signal-watches/{icpCriteriaID} openapi: 3.1.0 info: title: Tamtam Public API version: 2.0.0 servers: - url: https://api.tamtam.ai/api security: [] paths: /v2/icp-signal-watches/{icpCriteriaID}: put: tags: - ICP Signal Watches summary: Create or update an ICP signal watch description: >- 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. operationId: put-icp-signal-watch parameters: - description: >- ICP criteria UUID. Create one via [Create an ICP criteria](/api-reference/icp-criteria/create-an-icp-criteria). in: path name: icpCriteriaID required: true schema: description: >- ICP criteria UUID. Create one via [Create an ICP criteria](/api-reference/icp-criteria/create-an-icp-criteria). type: string - description: Target account UUID. Required for staff; ignored for customer keys. explode: false in: query name: account_id schema: description: >- Target account UUID. Required for staff; ignored for customer keys. type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/PutIcpSignalWatchInputBody' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/IcpSignalWatchDto' description: OK default: content: application/problem+json: schema: $ref: '#/components/schemas/ErrorModel' description: Error security: - apikeyAuth: [] - bearerAuth: [] components: schemas: PutIcpSignalWatchInputBody: additionalProperties: false properties: is_enabled: description: >- Defaults to true. Set false to record events without delivering them. examples: - true type: boolean news_topics: description: >- 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. examples: - - m_and_a items: type: string type: - array - 'null' signal_types: description: 'Signal types to detect. Supported: news, job_posting.' examples: - - news - job_posting items: type: string type: - array - 'null' required: - signal_types type: object IcpSignalWatchDto: additionalProperties: false properties: created_at: description: When the watch was first created. format: date-time type: string icp_criteria_id: description: The ICP whose matching companies are watched. type: string id: description: >- Watch UUID. Stable across reconfigurations; every endpoint keys on icp_criteria_id instead, so you rarely need this. type: string is_enabled: description: >- When false the watch keeps detecting and recording events but delivers nothing — useful to inspect what an ICP would produce before acting on it. type: boolean news_topics: description: News topics this watch searches. Empty means every supported topic. examples: - - m_and_a items: type: string type: - array - 'null' signal_types: description: Signal types this watch produces. examples: - - news - job_posting items: type: string type: - array - 'null' updated_at: description: When the watch was last reconfigured. format: date-time type: string required: - id - icp_criteria_id - signal_types - news_topics - is_enabled - created_at - updated_at type: object ErrorModel: additionalProperties: false properties: detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object securitySchemes: apikeyAuth: description: Account API key passed in the Authorization header in: header name: Authorization type: apiKey bearerAuth: description: Bearer JWT obtained via the OAuth 2.1 authorization flow scheme: bearer type: http ````