Skip to main content
POST
List 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.
  • p is a zero-based page number, not a byte offset — the server computes offset = p * limit internally.
  • orderby accepts updated_at or version; any other value silently falls back to updated_at.
  • limit defaults 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
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

Query parameters for paginating an application's rule history.

application_id
string
required

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

p
integer<int64>
default:0

Zero-based page number. Default 0.

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

Page size. Default 20, capped at 100; values ≤ 0 fall back to the default.

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

Sort column: updated_at or version. Unrecognized values fall back to updated_at.

asc
boolean
default:false

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.

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 error ingestion rule history.