Update a Signal

Updates the interaction_data of an existing signal.

Update a signal

PATCH/api/v2/partner/workspaces/{partner_workspace_id}/signals/{id}

Path parameters

Parameter	Type	Description
partner_workspace_id	string	Opaque workspace identifier from the partner system.
id	integer	Id of the signal.

Request body

Field	Type	Required	Description
interaction_data	any	No	Signal-type-specific payload to store, replacing the existing one.

Example request

curl -X PATCH "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/signals/301" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"interaction_data": {"keywords_found": ["AI", "growth"]}}'

Example response

{
  "data": {
    "id": 301,
    "signal_type": "keywordDetection",
    "data": { "keywords_found": ["AI", "growth"] },
    "detected_at": "2026-06-12T09:00:00.000Z",
    "signal_date": "2026-06-12T09:00:00.000Z",
    "lead_id": null,
    "company_id": 456,
    "agent_id": null,
    "source_url": null,
    "author": null,
    "excerpt": null
  }
}

Response fields

Field	Type	Description
id	integer	Id of the signal.
signal_type	string or null	Signal type.
data	any or null	Signal-type-specific payload.
detected_at	string or null	When the signal was detected (ISO 8601).
signal_date	string or null	Date associated with the signal event (ISO 8601).
lead_id	integer or null	ID of the associated lead, if any.
company_id	integer or null	ID of the associated company, if any.
agent_id	integer or null	ID of the agent that produced this signal, if any.
source_url	string or null	Link to the source content behind the signal. `null` when the signal has no public external link.
author	object or null	The person behind the source content, when known: `full_name`, `headline`, `linkedin_url` (each nullable). `null` for company-level or authorless signals.
excerpt	string or null	A short text excerpt from the source content. `null` when no text is available.

Errors

Status	Meaning
400	Invalid request body or `id` parameter.
401	The master key is missing or invalid.
403	The master key is not authorized to access this resource.
404	No signal found for this `id`.
429	Too many requests.
500	An unexpected server error occurred.

Error responses use RFC 9457 problem documents with Content-Type: application/problem+json.