Skip to main content
POST
List preset severity rule history

Restrictions

Usage

  • Each entry is an application-level snapshot of every rule as it existed immediately before the mutation that produced it — not a diff. A fresh snapshot is written before every create/update/enable/disable/delete/reorder/revert call that actually changes something — an update carrying none of the mutable fields returns success without writing one — so version=1 is typically an empty rule set captured just before the first rule was ever created.
  • rules items carry the full internal row (including account_id, created_by, id, deleted_at), which is a wider shape than the one returned by rules/list.
  • limit defaults to 20 and is silently capped at 100 rather than rejected.
  • orderby accepts only updated_at or version; any other value (including omitted) falls back to updated_at rather than erroring.
  • Results sort descending by default; pass asc=true for ascending order.

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

Filters for listing preset severity rule change history.

application_id
string
required

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

p
integer
default:0

Zero-based page number.

Required range: x >= 0
limit
integer
default:20

Page size. Values <= 0 default to 20; values above 100 are capped at 100.

Required range: x <= 100
orderby
enum<string>
default:updated_at

Sort column. Any other value (including omitted) falls back to updated_at.

Available options:
updated_at,
version
asc
boolean
default:false

Sort ascending when true; results are descending by default.

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

Paginated list of preset severity rule history snapshots.