Get a Signal Detection
Retrieve a single signal detection by ID.
GET/api/v2/workspace/signals/{id}
Path parameters
| Parameter | Type | Description |
|---|---|---|
| id | integer | Numeric SQL id of the detection (the id field from the list endpoint). A detection belonging to another workspace returns 404. |
Example request
curl "https://api.getsillage.com/api/v2/workspace/signals/101" \
-H "Authorization: Bearer $SILLAGE_API_KEY"Example response
200 OK
{
"data": {
"id": 101,
"signal_type": "keywordDetection",
"data": {
"content_id": 5100,
"author": {
"type": "profile",
"full_name": "Jane Doe",
"headline": "VP Product at Acme",
"linkedin_url": "https://linkedin.com/in/janedoe"
},
"keywords_found": ["AI"]
},
"detected_at": "2026-06-01T10:00:00.000Z",
"signal_date": null,
"lead_id": 456,
"company_id": 789,
"agent_id": 12,
"source_url": "https://www.linkedin.com/feed/update/urn:li:activity:7100000000000000000/",
"author": {
"full_name": "Jane Doe",
"headline": "VP Product at Acme",
"linkedin_url": "https://linkedin.com/in/janedoe"
},
"excerpt": "Excited to share how AI is transforming our product roadmap this quarter."
}
}Errors
| Status | Meaning |
|---|---|
| 400 | Invalid path parameter. |
| 401 | The API key is missing or invalid. |
| 403 | The workspace does not have access to this resource. |
| 404 | Detection not found or belongs to another workspace. |
| 429 | Rate limit exceeded. |
| 500 | An unexpected server error occurred. |
Error responses use RFC 9457 problem documents with Content-Type: application/problem+json:
{
"type": "https://docs.getsillage.com/errors/not-found",
"title": "Not Found",
"status": 404,
"detail": "Signal detection not found.",
"instance": "/api/v2/workspace/signals/101"
}