Skip to main content
POST
Delete a behavior event

Restrictions

Usage

  • Deletion is refused with ReferenceExist while a saved funnel still uses the event; move those funnels to another step first.
  • The event disappears from the list; its history is kept.
  • 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

Address one behavior event of an application.

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).

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.