Skip to main content
POST
Enable an error ingestion rule

Restrictions

Usage

  • Enabling a rule that is already enabled succeeds and still writes a history version.
  • Returns ResourceNotFound if rule_id doesn’t exist (or was deleted) under application_id.
  • Each write first saves the application’s whole rule set, as it was before the change, as a new history version.
  • Ingestion reads enabled rules from a per-application cache that lives 5 seconds, so the change applies to newly ingested errors within about 5 seconds.
  • Requires edit access to 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

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

Empty response body on success.