Skip to main content
POST
List error ingestion rule history

Restrictions

Usage

  • You need read access to the target application before calling this operation.
  • Snapshots contain the entire rule set for the application.

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 listing rule-set history snapshots.

application_id
string
required

RUM application ID.

p
integer<int64>

Zero-based page number.

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

Snapshot count per page. Defaults to 20 and is capped at 100.

orderby
enum<string>

Snapshot sort field.

Available options:
updated_at,
version
asc
boolean

Sort ascending when true.

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-set history.