Skip to main content
POST
Restore error ingestion rule history

Restrictions

Usage

  • You need write access to the target application before calling this operation.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.
  • The selected snapshot replaces the application’s complete rule set.

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

Parameters for restoring a rule-set snapshot.

application_id
string
required

RUM application ID.

version
integer
required

History snapshot version to restore.

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

Endpoint-specific payload. See each operation's 200 response schema.