Skip to main content
POST
Revert error ingestion rules to a history version

Restrictions

Usage

  • Revert replaces the entire rule set for the application — rules created after the target version are removed, not merged.
  • The current state is snapshotted into history before the revert runs, so a revert can itself be undone by reverting again.
  • Returns InvalidParameter (not ResourceNotFound) when version doesn’t exist for the application.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

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

Selects the history version to revert an application's rules to.

application_id
string
required

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

version
integer
required

History version number to revert to. Get versions via POST /rum/error-ingestion/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
required

Empty response body on success.