List in-flight signal runs

Returns all the signal runs that are in progress for your workspace. This is a snapshot, not a page: an empty data array means no run is in progress. Each item is the run described in Signal Runs, with a status of pending or in_progress. The runs are sorted from the newest to the oldest.

Route

GET/api/v3/signal-runs

Access modes

Use a workspace API key. The workspace is inferred from the key.

Authorization: Bearer sk_live_...

Example request

curl "https://api.getsillage.com/api/v3/signal-runs" \
  -H "Authorization: Bearer $SILLAGE_API_KEY"

Success response

Status: 200 OK

{
  "data": [
    {
      "id": 5,
      "status": "in_progress",
      "label": "Detecting signals",
      "created_at": "2026-01-15T09:30:00.000Z",
      "updated_at": "2026-01-15T09:30:00.000Z",
      "companies": [
        {
          "id": 88,
          "name": "Acme",
          "domain": "acme.com",
          "linkedin_url": "https://www.linkedin.com/company/acme",
          "linkedin_handle": "acme",
          "logo_url": "https://example.com/acme-logo.png"
        }
      ],
      "signal_setup_id": 42
    }
  ]
}

Response fields

data is an array with one run per element:

Field	Type	Description
id	integer	ID of the signal run.
status	string	Where the run stands: `pending`, `in_progress`, `completed` or `failed`. See Run statuses.
label	string	A short readable description of the current step.
created_at	string (date-time)	When the run was started.
updated_at	string (date-time)	When the run was last updated.
companies	array	The accounts being scanned. An empty array means the run covers the whole workspace.
companies[].id	integer	ID of the company, as returned by `POST /v3/companies/query`.
companies[].name	string \| null	Company name.
companies[].domain	string \| null	Company domain.
companies[].linkedin_url	string \| null	LinkedIn page of the company.
companies[].linkedin_handle	string \| null	LinkedIn handle of the company.
companies[].logo_url	string \| null	Logo of the company.
signal_setup_id	integer \| null	ID of the signal setup the run belongs to, the same ID as in the client's signal setups. `null` when the run is not tied to one of the signal setups, for example a very old run, or a setup deleted while it was running.

Use signal_setup_id to show which of your signal setups are running right now.

Errors

Status	Meaning
401	The API key is missing or invalid.
422	A query parameter is sent: this route takes none, and `errors` names the parameter.
429	Rate limit exceeded.
500	An unexpected server error occurred.

Error responses use RFC 9457 problem documents with Content-Type: application/problem+json. type is always about:blank; code tells one problem from another, detail says what went wrong this time, and errors names the field at fault.