Revert preset severity rules to a history snapshot
Issue preset severity rules
Revert preset severity rules to a history snapshot
Roll back preset severity rules to the state captured in a specific history snapshot.
POST
Revert preset severity rules to a history snapshot
Restrictions
Usage
- Replaces the entire current rule set with the snapshot’s rows:
rule_id,priority,filters,severity,status, andcreated_byare preserved from the snapshot, butcreated_at/updated_atare reset to the revert time andupdated_byis set to the reverting user. - Returns
InvalidParameter(notResourceNotFound) whenversiondoes not correspond to an existing history snapshot for the application. - The revert itself is captured as a new history snapshot before it is applied, so a revert can itself be reverted.
- Every call is recorded in the account audit log. Don’t put secrets in request fields.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
application/json
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.