List signal setups

Lists every signal your workspace has set up.

Route

GET/api/v3/signal-setups

Access modes

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

Authorization: Bearer sk_live_...

Query parameters

See Pagination for the shared page / page_size parameters.

Example request

curl "https://api.getsillage.com/api/v3/signal-setups?page=1&page_size=25" \
  -H "Authorization: Bearer $SILLAGE_API_KEY"

Success response

Status: 200 OK

{
  "data": [
    {
      "id": 42,
      "signal_template_id": 3,
      "name": "Acme keywords",
      "status": "enabled",
      "parameters": { "keywords": ["acme"], "scopes": ["discovery"] },
      "schedule": null,
      "created_at": "2026-09-18T12:00:00.000Z"
    }
  ],
  "meta": {
    "pagination": {
      "page": 1,
      "page_size": 25,
      "page_count": 1,
      "total": 1
    }
  }
}

Response fields

Field	Type	Description
data[].id	integer	ID of the signal setup. Specific to your environment.
data[].signal_template_id	integer	ID of the signal this setup is for.
data[].name	string	Display name for this setup.
data[].status	string	`enabled` or `disabled`.
data[].parameters	object	This setup's own answers, exactly as sent.
data[].schedule	object or null	`null`, or `{ "cadence": "weekly" }` when this setup runs on its own.
data[].created_at	string	When this setup was created.
meta.pagination	object	Pagination metadata — see Pagination.

Errors

Status	Meaning
400	Invalid `page` or `page_size`.
401	The API key is missing or invalid.
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 on v3 — title is what tells one problem from another.