List a client's signal setups
Browse the signals one of your clients has set up.
Lists every signal the named client has set up. Filter by persona with persona_id. Signal setups are sorted from the oldest to the newest.
Route
GET/api/v3/partner/workspaces/{partner_workspace_id}/signal-setups
Path parameters
| Parameter | Type | Description |
|---|---|---|
| partner_workspace_id | string | Your own ID for the client workspace, as you chose it at creation. URL-encode it in the path. |
Query parameters
| Parameter | Type | Description |
|---|---|---|
| page | integer | Page number. Defaults to 1. Must be greater than or equal to 1. |
| page_size | integer | Number of items per page. Defaults to 25. Must be between 1 and 100. |
| persona_id | integer | Only the setups of this persona, plus the ones tied to no persona. Give the ID of a persona of the client's workspace, from List personas. Leave it out to get every setup. |
Example request
curl "https://api.getsillage.com/api/v3/partner/workspaces/ws_123/signal-setups?page=1&page_size=25&persona_id=7" \
-H "Authorization: Bearer $SILLAGE_MASTER_KEY"Success response
Status: 200 OK
{
"data": [
{
"id": 42,
"signal_template": {
"id": 2,
"key": "mentioned-my-brand",
"name": "Mentioned my brand",
"description": "Detect when prospects mention your brand on LinkedIn.",
"row_summary": "Posts naming your product anywhere on LinkedIn.",
"category": "my_network",
"status": "live",
"subjects": ["person"],
"scopes": ["discovery", "account_monitoring"],
"tags": [],
"pricing": {
"account_monitoring": {
"signal_bucket": "essential",
"credits": 50,
"unit": "per_key_account_per_month"
},
"discovery": {
"credits": 20,
"unit": "signal_found"
}
},
"archived_at": null
},
"name": "Acme brand mentions",
"status": "enabled",
"parameters": {
"scopes": ["discovery"],
"keywords": ["acme.com"]
},
"schedule": null,
"persona_id": 7,
"created_at": "2026-09-18T12:00:00.000Z",
"last_detected_at": "2026-09-20T08:30:00.000Z"
}
],
"meta": {
"pagination": {
"page": 1,
"page_size": 25,
"page_count": 1,
"total": 1
}
}
}Response fields
| Field | Type | Description |
|---|---|---|
| data[] | array | The signal setups of the page. |
| meta.pagination | object | Pagination metadata: page, page_size, page_count and total. See Pagination. |
Each item of data has the same fields as Get a client's signal setup.
Errors
| Status | Meaning |
|---|---|
| 401 | The master key is missing or invalid. |
| 404 | No workspace found for this partner_workspace_id. |
| 422 | page, page_size or persona_id is not valid, for example a persona_id that is not a persona of the workspace. Also returned when partner_workspace_id is 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; code tells one problem from another, detail says what went wrong this time, and errors names the field at fault.