Get Suppression
API key access
compliance:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/suppressions/{suppression_id}Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Path Parameters
uuidHeader Parameters
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/suppressions/497f6eca-6276-4993-bfeb-53cbbbba6f08" \ -H "X-Workspace-Id: string"{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"workspace_id": "0967198e-ec7b-4c6b-b4d3-f71244cadbe9",
"kind": "email",
"value": "string",
"reason": "opt_out",
"channels": [
"email"
],
"source": "string",
"note": "string",
"created_by": "ee824cad-d7a6-4f48-87dc-e8461a9201c4",
"created_at": "2019-08-24T14:15:22Z"
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}Get Contact Pressure
The cross-channel contact-pressure rules this workspace sends and calls under (touches per person, company and recipient domain, gaps, the cool-down after a negative reply), the resource rate limits it can lower, its own overrides and what applies after them. Cold touches (sequences) get every rule; a person's one-off action is exempt while the lead is in a conversation with us; lead-initiated threads (reply drafts, requested callbacks, speed-to-lead) are exempt.
List Consents
The lead's consent records, newest first.