Count Signal Detections
Get the total number of signal detections matching your filters.
GET/api/v2/workspace/signals/count
Returns the total number of published signal detections matching the given filters. Accepts the same filter parameters as the query endpoint (signal_start_date, signal_end_date, detection_start_date, detection_end_date, agent_id, signal_run_id, company_id, company_domain, company_linkedin_handle, company_linkedin_url, lead_id, countries, cities). The cursor and limit parameters are ignored. When signal_start_date is omitted, it defaults to 90 days before now; it cannot go further back than 180 days — an older value is clamped to that limit.
Example request
curl "https://api.getsillage.com/api/v2/workspace/signals/count" \
-H "Authorization: Bearer $SILLAGE_API_KEY"Example response
200 OK
{
"total": 42
}Errors
| Status | Meaning |
|---|---|
| 400 | Invalid query parameters. |
| 401 | The API key is missing or invalid. |
| 403 | The workspace does not have access to this resource. |
| 404 | Returned when string company identifier(s) (company_domain, company_linkedin_handle, or company_linkedin_url) were supplied and none resolved to a known company in your workspace. company_id is never validated and never triggers a 404. |
| 429 | Rate limit exceeded. |
| 500 | An unexpected server error occurred. |
Error responses use RFC 9457 problem documents with Content-Type: application/problem+json.