Skip to main content
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, and created_by are preserved from the snapshot, but created_at/updated_at are reset to the revert time and updated_by is set to the reverting user.
  • Returns InvalidParameter (not ResourceNotFound) when version does 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.
  • Requires edit rights on the application (account owner or admin, the application’s creator, or a member of its team); otherwise returns AccessDenied. An unknown application_id returns ResourceNotFound.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for reverting to a history snapshot.

application_id
string
required

RUM application ID. Get application IDs via POST /rum/application/list.

version
integer
required

Snapshot version number to revert to. Get versions via POST /rum/issue/preset-severity/rules/history/list.

Required range: x >= 1

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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.