Skip to main content
POST
List error ingestion rules

Restrictions

Usage

  • Deleted rules are excluded; only rules with status enabled or disabled are returned.
  • Rules are ordered newest-created first. The list is not paginated.
  • 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 listing an application's error ingestion rules.

application_id
string
required

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

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

All error ingestion rules configured for the application.