Skip to main content
POST
Update preset severity rule

Restrictions

Usage

  • Only fields present in the request are changed; omitted fields keep their current value.
  • Returns ResourceNotFound if rule_id does not exist in the application.
  • If filters is provided it replaces the entire filter structure and is revalidated against the same allowed key set as create.
  • 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 updating a preset severity rule. Only provided fields are changed.

application_id
string
required

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

rule_id
string
required

Rule ID to update. Get rule IDs via POST /rum/issue/preset-severity/rules/list.

description
string | null

New description, up to 512 characters. Omit to leave unchanged.

Maximum string length: 512
filters
object[][]

New OR-of-ANDs filter structure; replaces the whole current structure. Omit or pass null to leave unchanged. The outer array is OR'd, each inner array is AND'd; an empty outer array never matches, an empty inner group matches every error.

rule_name
string | null

New display name, 1-128 characters. Omit to leave unchanged.

Required string length: 1 - 128
severity
enum<string> | null

New severity. Omit to leave unchanged.

Available options:
Critical,
Warning,
Info

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.