Skip to main content
POST
Create preset severity rule

Restrictions

Usage

  • You need write access to the target application before calling this operation.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

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

application_id
string
required

RUM application ID.

rule_name
string
required

Rule name within the application.

Required string length: 1 - 128
filters
object[][]
required

Filter groups joined by OR; each group joins its conditions with AND.

Conditions joined by AND.

severity
enum<string>
required

Severity assigned by this rule.

Available options:
Critical,
Warning,
Info
description
string

Optional rule explanation.

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
required

Identifier, name, and priority of the created preset severity rule.