List preset severity rule history
Return the change history of preset severity rules for a RUM application.
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
updatecarrying none of the mutable fields returns success without writing one — soversion=1is typically an empty rule set captured just before the first rule was ever created. rulesitems carry the full internal row (includingaccount_id,created_by,id,deleted_at), which is a wider shape than the one returned byrules/list.limitdefaults to 20 and is silently capped at 100 rather than rejected.orderbyaccepts onlyupdated_atorversion; any other value (including omitted) falls back toupdated_atrather than erroring.- Results sort descending by default; pass
asc=truefor ascending order.
Authorizations
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
Filters for listing preset severity rule change history.
RUM application ID. Get application IDs via POST /rum/application/list.
Zero-based page number.
x >= 0Page size. Values <= 0 default to 20; values above 100 are capped at 100.
x <= 100Sort column. Any other value (including omitted) falls back to updated_at.
updated_at, version 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.