curl -X POST https://api.up2data.ai/v1/signals/sig_9dk2m1xq/pause \
-H "X-API-Key: $UP2DATA_API_KEY"
{
"data": { "id": "sig_9dk2m1xq", "status": "paused", "paused_reason": "user" },
"meta": { "creditsUsed": 0, "billed": false, "reason": "signal_paused", "requestId": "req_pp1x02mn" }
}
Signals
Pause a Signal
Stop scheduled checks without losing state.
POST
/
v1
/
signals
/
{id}
/
pause
curl -X POST https://api.up2data.ai/v1/signals/sig_9dk2m1xq/pause \
-H "X-API-Key: $UP2DATA_API_KEY"
{
"data": { "id": "sig_9dk2m1xq", "status": "paused", "paused_reason": "user" },
"meta": { "creditsUsed": 0, "billed": false, "reason": "signal_paused", "requestId": "req_pp1x02mn" }
}
Cost: Free — and a paused Signal bills nothing.
The snapshot is kept, so on resume the next check diffs against the last known state — a change that happened while paused still triggers.
How Signals work
Signals are scheduled change monitoring, billed per check. See what you can watch and how it’s priced.
string
required
Bulk pause by tag
POST /v1/signals/pause (no ID) pauses a whole fleet at once:
curl -X POST https://api.up2data.ai/v1/signals/pause \
-H "X-API-Key: $UP2DATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "tag": "q3-pipeline" }'
# → { "data": { "paused": 412 }, ... }
curl -X POST https://api.up2data.ai/v1/signals/sig_9dk2m1xq/pause \
-H "X-API-Key: $UP2DATA_API_KEY"
{
"data": { "id": "sig_9dk2m1xq", "status": "paused", "paused_reason": "user" },
"meta": { "creditsUsed": 0, "billed": false, "reason": "signal_paused", "requestId": "req_pp1x02mn" }
}