Docs
OverviewGuidesZero & MCPAPI referenceChangelog
Signals

Delete Signal Rule

Delete a rule (admin+). Signals it already acted on keep their record.

API key access

Needs the admin scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
DELETE/api/v1/signal-rules/{rule_id}

Authorization

AuthorizationBearer <token>

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

rule_idstring
Formatuuid

Header Parameters

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

Response Body

curl -X DELETE "http://localhost:8000/api/v1/signal-rules/497f6eca-6276-4993-bfeb-53cbbbba6f08" \  -H "X-Workspace-Id: string"
Empty
Empty
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}

Create Signal Rule

Add a trigger rule (admin+): when a new signal matches its kinds and keywords, `notify` (flag the signal and send a `signal.triggered` webhook) or `enroll` up to `max_leads` of the company's leads into an active sequence. Enrolling checks reachability, consent and suppressions per lead; contact pressure, calling windows and send caps apply when steps run. 409 over `SIGNALS_MAX_RULES`.

List Signal Rules

The workspace's trigger rules, oldest first.