Skip to main content
POST
List preset severity rules

Restrictions

Usage

  • Rules are returned ordered by priority ascending, then created_at ascending — the same order they are evaluated in.
  • Only enabled rules are evaluated against incoming errors; the first enabled rule (in priority order) whose filters match an error wins and assigns its severity. Errors matching no enabled rule get a built-in severity: crashes are Critical, other errors are scored by environment and message keywords.
  • Severity is decided once, when an error creates a new issue; a rule change affects only errors ingested afterwards (enabled rules are cached for up to 5 seconds) and never re-grades existing issues.
  • Rules of a private application can be read only by callers with edit rights on it (account owner or admin, its creator, or a member of its team); others get 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

Parameters for listing preset severity 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

Operation-specific payload, documented in each operation's 200 response. Operations without a payload return {} or omit data entirely.