Skip to main content
POST
Create preset severity rule

Restrictions

Usage

  • filters.*.key accepts only a fixed set of Error-level attributes; any other key returns InvalidParameter.
  • Pass at least one condition group: an empty filters array is accepted but produces a rule that can never match.
  • The new rule is created enabled and appended with the lowest evaluation precedence (priority = current max + 1); use the reorder operation to move it earlier.
  • Requires edit rights on the application (account owner or admin, the application’s creator, or a member of its team); otherwise returns AccessDenied. An unknown application_id returns ResourceNotFound.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

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 creating a preset severity rule.

application_id
string
required

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

filters
object[][]
required

OR-of-ANDs filter structure: the outer array is OR'd, each inner array is AND'd. A rule matches an error when at least one inner AND-group fully matches. An empty outer array never matches; an empty inner group matches every error.

rule_name
string
required

Rule display name, 1-128 characters.

Required string length: 1 - 128
severity
enum<string>
required

Severity to assign to errors matching this rule.

Available options:
Critical,
Warning,
Info
description
string

Optional description, up to 512 characters.

Maximum string length: 512

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.