Skip to main content
POST
Update an error ingestion rule

Restrictions

Usage

  • Only fields present in the request are changed; omitted fields keep their current value.
  • Calling update with no fields set is a no-op that still returns success.
  • Returns ResourceNotFound if rule_id doesn’t exist under application_id.
  • 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

Partial update to an existing error ingestion rule. Omitted fields are left unchanged.

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/error-ingestion/rules/list.

rule_name
string | null

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

Required string length: 1 - 128
description
string | null

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

Maximum string length: 512
filters
object[][]

New filter conditions. Omit to leave unchanged.

AND-group. The group only matches when every condition inside it matches.

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

Empty response body on success.