Skip to main content
POST
List error ingestion rule history

Restrictions

Usage

  • Each write first saves the rule set as it was before the change, so version N holds the rules just before the Nth change, and its updated_by/updated_at identify that change. The current rule set is returned by list, not here.
  • One history item is a full snapshot of every non-deleted rule for the application, not a diff of a single rule.
  • p is a zero-based page number: the server skips p * limit items.
  • limit defaults to 20 and is capped at 100; values above 100 are clamped, values of 0 or below fall back to the default.
  • Any member can read a public application; a private application requires edit access (account owner or admin, its creator, or a member of its team), otherwise AccessDenied. An unknown application_id returns ResourceNotFound.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

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.

asc
boolean
default:false

true sorts ascending; false (default) sorts descending, newest first.

limit
integer<int64>
default:20

Page size. Default 20; values above 100 are clamped to 100, and values of 0 or below fall back to 20.

orderby
enum<string>
default:updated_at

Sort column:

  • updated_at: time of the change that created the version (default).
  • version: version number. Any other value falls back to updated_at.
Available options:
updated_at,
version
p
integer<int64>
default:0

Zero-based page number. Default 0.

Required range: x >= 0

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

Paginated error ingestion rule history.