Skip to main content
POST
Cost: Free to create · each scheduled check bills the underlying scrape (pay-per-check) · the first check establishes the baseline (billed, never triggers)

How Signals work

Signals are scheduled change monitoring, billed per check. See what you can watch and how it’s priced.
Creates a durable monitoring rule. Creating many Signals from one template? Use bulk create.
string
required
Human-readable label, shown in notifications and the dashboard.
string[]
Free-form labels for fleet management — filter lists and bulk pause/resume by tag.
string
Optional platform attribution key (1–256 characters). Filter lists and roll up usage with GET /v1/usage/signals.
object
Opaque JSON bag (max 8192 bytes serialized). Copied onto Triggers and webhook payloads for your tenant context.
boolean
default:"true"
Create paused by setting false.
object
required
object
required
object
required
object
Webhook destination — or omit entirely to use your account’s default webhook.

Response

object
The Signal, including id, status, estimated_monthly_credits, credits_used_this_month, and next_check_at. The first check establishes the baseline snapshot — it is billed like any check, can never trigger, and appears in check logs with reason: "baseline_established".
Signals pause — never silently skip — on insufficient balance, a blown monitoring budget, or a dead webhook URL. Each pause fires a signal.paused event with the reason.