curl -X PATCH https://api.up2data.ai/v1/signals/sig_9dk2m1xq \
-H "X-API-Key: $UP2DATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "schedule": { "interval": "7d" } }'
{
"data": {
"id": "sig_9dk2m1xq",
"schedule": { "interval": "7d", "timezone": "America/New_York" },
"estimated_monthly_credits": 4,
"next_check_at": "2026-07-14T09:00:00Z"
},
"meta": { "creditsUsed": 0, "billed": false, "reason": "signal_updated", "requestId": "req_u8n1mp3a" }
}
Signals
Update a Signal
Change schedule, criteria, or webhook in place — no recreate needed.
PATCH
/
v1
/
signals
/
{id}
curl -X PATCH https://api.up2data.ai/v1/signals/sig_9dk2m1xq \
-H "X-API-Key: $UP2DATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "schedule": { "interval": "7d" } }'
{
"data": {
"id": "sig_9dk2m1xq",
"schedule": { "interval": "7d", "timezone": "America/New_York" },
"estimated_monthly_credits": 4,
"next_check_at": "2026-07-14T09:00:00Z"
},
"meta": { "creditsUsed": 0, "billed": false, "reason": "signal_updated", "requestId": "req_u8n1mp3a" }
}
Cost: Free
Partial update: send only the fields you’re changing. The snapshot history is preserved, so tightening criteria doesn’t cause spurious re-triggers.
How Signals work
Signals are scheduled change monitoring, billed per check. See what you can watch and how it’s priced.
string
required
string
string[]
string
Platform attribution key (1–256 characters), or
null to clear. Past check usage keeps the snapshotted value at check time.object
Opaque JSON bag (max 8192 bytes serialized). Replaces the previous bag when set.
object
object
curl -X PATCH https://api.up2data.ai/v1/signals/sig_9dk2m1xq \
-H "X-API-Key: $UP2DATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "schedule": { "interval": "7d" } }'
{
"data": {
"id": "sig_9dk2m1xq",
"schedule": { "interval": "7d", "timezone": "America/New_York" },
"estimated_monthly_credits": 4,
"next_check_at": "2026-07-14T09:00:00Z"
},
"meta": { "creditsUsed": 0, "billed": false, "reason": "signal_updated", "requestId": "req_u8n1mp3a" }
}