List error ingestion rule history
Return paginated snapshots of an application’s error ingestion rule history.
Restrictions
Usage
- One history item is a full snapshot of every rule for the application at that point in time, not a diff of a single rule.
pis a zero-based page number, not a byte offset — the server computesoffset = p * limitinternally.orderbyacceptsupdated_atorversion; any other value silently falls back toupdated_at.limitdefaults to 20 and is capped at 100 server-side; values above 100 are silently clamped, values of 0 or below fall back to the default.
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
Query parameters for paginating an application's rule history.
RUM application ID. Get application IDs via POST /rum/application/list.
Zero-based page number. Default 0.
x >= 0Page size. Default 20, capped at 100; values ≤ 0 fall back to the default.
x <= 100Sort column: updated_at or version. Unrecognized values fall back to updated_at.
Sort ascending instead of the default descending order.
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.