curl -X POST \
-H "Content-Type: application/json" \
-d '{}' \
"https://api.particle.pro/v1/alerts/disable"{
"alert_id": "<string>",
"already_disabled": true,
"delivery_cadence": "<string>",
"is_active": true,
"kind": "<string>",
"manage_url": "<string>",
"monitor_id": "<string>",
"title": "<string>"
}{
"detail": "Property foo is required but is missing.",
"error_code": "<string>",
"errors": [
{
"location": "<string>",
"message": "<string>",
"value": "<unknown>"
}
],
"instance": "https://example.com/error-log/abc123",
"resolve": {
"message": "<string>",
"action": "<string>",
"endpoint": "<string>",
"method": "<string>",
"url": "<string>"
},
"status": 400,
"title": "Bad Request",
"type": "https://example.com/errors/example"
}Disable an alert via email-footer token
Redeems a single-use token from the footer of an alert email and flips the alert’s is_active flag to false. Idempotent: a replay returns 200 with already_disabled=true. Public — token possession is the auth factor.
curl -X POST \
-H "Content-Type: application/json" \
-d '{}' \
"https://api.particle.pro/v1/alerts/disable"{
"alert_id": "<string>",
"already_disabled": true,
"delivery_cadence": "<string>",
"is_active": true,
"kind": "<string>",
"manage_url": "<string>",
"monitor_id": "<string>",
"title": "<string>"
}{
"detail": "Property foo is required but is missing.",
"error_code": "<string>",
"errors": [
{
"location": "<string>",
"message": "<string>",
"value": "<unknown>"
}
],
"instance": "https://example.com/error-log/abc123",
"resolve": {
"message": "<string>",
"action": "<string>",
"endpoint": "<string>",
"method": "<string>",
"url": "<string>"
},
"status": 400,
"title": "Bad Request",
"type": "https://example.com/errors/example"
}Body
Disable-alert token from the footer of an alert email.
Response
OK
The alert identified by the supplied token.
True when this click is not the one that changed state — either the token was already redeemed (GET preview after a click, or POST replay), or the alert was already inactive when the token was redeemed. The is_active field reflects the alert's current state, which can diverge from already_disabled if the alert was re-enabled after the token was redeemed.
The alert's delivery cadence (REALTIME, DAILY, or WEEKLY).
The alert's current is_active flag — false after a successful POST.
The alert's kind (ENTITY_MENTION or PODCAST_SPEAKER).
Deep-link to the alert's management page.
Deprecated — use alert_id. The alert identified by the supplied token.
The alert's current title.
Was this page helpful?