Launch a signal run

Starts a detection run for a signal setup across the accounts of your workspace. The signal type comes from the signal setup, you do not send it. The run starts immediately and the response is 202 Accepted: follow it with Get a signal run until its status is completed or failed.

A launch starts one run per direction (inbound and outbound) for a signal setup that watches a competitor, partner or influencer list, plus one Discovery run when scopes includes discovery: up to three runs. A keyword signal setup starts one run, plus one Discovery run when scopes includes discovery. Any other signal setup starts one run. Each run is one element of data, and each has its own id to follow.

A signal setup runs one at a time. Launching it while one of its runs is still in progress returns 409: follow the run to completion first. A disabled signal setup cannot be launched and also returns 409.

A launch with nothing to check also returns 409, and nothing is started: none of the accounts the signal setup checks is monitored right now (no_monitored_account, or no_covered_account when they are turned on but unpaid). To see which accounts are monitored, open the Key accounts page or call GET /v3/lists/{kind}/{list_id}/members?monitoring_status=not_monitored (or not_covered).

There is no idempotency key: sending the same launch twice starts two runs and may charge twice. Before you retry, check the state with GET /v3/signal-runs (the runs in progress) or GET /v3/requests-status. A launch sent while a run of the same signal setup is in progress answers 409.

Route

Access modes

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

Authorization: Bearer sk_live_...

Body parameters

Example request

curl -X POST "https://api.getsillage.com/api/v3/signal-runs" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"signal_setup_id":42,"parameters":{"lookback_days":90}}'

Success response

Status: 202 Accepted

{
  "data": [
    {
      "id": 12345,
      "status": "in_progress",
      "label": "Detecting signals",
      "created_at": "2026-01-15T09:30:00.000Z",
      "updated_at": "2026-01-15T09:30:00.000Z",
      "companies": [],
      "signal_setup_id": 42
    }
  ]
}

A signal setup that starts two runs answers two elements:

{
  "data": [
    {
      "id": 12345,
      "status": "in_progress",
      "label": "Detecting signals",
      "created_at": "2026-01-15T09:30:00.000Z",
      "updated_at": "2026-01-15T09:30:00.000Z",
      "companies": [],
      "signal_setup_id": 42
    },
    {
      "id": 12346,
      "status": "in_progress",
      "label": "Detecting signals",
      "created_at": "2026-01-15T09:30:00.000Z",
      "updated_at": "2026-01-15T09:30:00.000Z",
      "companies": [],
      "signal_setup_id": 42
    }
  ]
}

Response fields

data is an array with one run per element:

Errors

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.