Skip to main content
POST
Disable an error ingestion rule

Restrictions

Usage

  • A disabled rule is kept and still returned by list, but is skipped when matching incoming errors.
  • 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

Identifies a single rule within an application.

application_id
string
required

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

rule_id
string
required

Rule ID. Get rule IDs via POST /rum/error-ingestion/rules/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
required

Empty response body on success.