Poll Signal Run

Returns the current status of a signal run. Poll this endpoint after calling POST .../signal-runs until stage is completed or failed.

Poll a signal run

GET/api/v2/partner/workspaces/{partner_workspace_id}/signal-runs/{id}

Parameter	Type	Description
partner_workspace_id	string	Opaque workspace identifier from the partner system.
id	integer	Id of the signal run (`signal_request_id` from the launch response).

curl "https://api.getsillage.com/api/v2/partner/workspaces/ws_123/signal-runs/501" \
  -H "Authorization: Bearer $SILLAGE_API_KEY"

{
  "signal_request_id": 501,
  "stage": "completed",
  "metadata": null
}

When some accounts could not be scanned, metadata reports them so you can retry:

{
  "signal_request_id": 501,
  "stage": "completed_partial",
  "metadata": { "failed": { "dropped_account_ids": [202, 203] } }
}

Field	Type	Description
signal_request_id	integer	Id of the run.
stage	string	Processing stage. Poll until `completed`, `completed_partial`, or `failed`.
metadata	object or null	Accounts that were not scanned (`failed.dropped_account_ids`). `null` when every account was scanned or when the run failed entirely (`failed`).
metadata.failed.dropped_account_ids	array of integers	IDs of accounts that could not be scanned in this run.

Status	Meaning
400	Invalid `id` path parameter.
401	The master key is missing or invalid.
403	The master key is not authorized to access this resource.
404	No signal run 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.