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

Restrictions

Usage

  • Version N holds the rules as they were just before the Nth change, so reverting to version N undoes change N and every later change.
  • Revert replaces the entire rule set for the application: rules that are not in the target version are removed, not merged.
  • Restored rules keep their rule_id, name, description, filters, and status; their created_at and updated_at are reset to the revert time.
  • The current state is saved as a new history version 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.
  • Ingestion reads enabled rules from a per-application cache that lives 5 seconds, so the change applies to newly ingested errors within about 5 seconds.
  • Requires edit access to 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

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

Empty response body on success.