Skip to main content
POST
Update a behavior event

Restrictions

Usage

  • Behavior events never rewrite stored data: rules are evaluated at query time, so a new or edited event applies to the whole retention window immediately.
  • Omitted fields keep their stored value. A change to name or rules bumps version and stores a history snapshot; a description-only edit does not.
  • The call is recorded in the account audit log.

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

Change a behavior event's name, description or rules.

application_id
string
required

RUM application ID. The caller needs read access to it; for write operations, manage access.

event_id
string
required

Behavior event ID (a short UUID assigned at creation).

description
string | null

New description. Omit to keep the current one; a description-only edit does not bump version.

Maximum string length: 512
name
string | null

New name. Omit to keep the current one; a name or rule change bumps version.

Required string length: 1 - 128
rules
object[]

Replacement rules. Omit to keep the current ones. 1-20 rules.

Required array length: 1 - 20 elements

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

A saved behavior event: a named rule set evaluated at query time.