PIpixiebrix
support

POST /api/support/users/{id}/activity/security-events/

Changed on

Create test security events for a single user in one of their organizations, for QA and evaluation. The organization must have the activity-tracking flag enabled. An omitted category, severity, or action is chosen at random per event, and each event is tagged data.test_event. Events are attributed to the user's primary activity policy and, unless skip_alerts is set, queue security alert emails the same way ingested events do. Support staff only.

Request

  • Base URL
    https://app.pixiebrix.com
  • Auth
    none declared

Path parameters

idstring required

Request body

organization_idstring uuid required

Organization to create the events in. Must be one the user is an active member of, with activity tracking enabled.

category'ai_prompt_dlp' | 'ai_tool_access' | 'clipboard' | 'site_access' | 'file_upload' | 'form_dlp' | 'protected_field_edit' | 'prohibited_language' | 'text_pattern_match' | 'element_redaction' | 'address_fraud_match' | 'interaction_match' | 'print' | 'screenshot'

Event category. Omit to pick one at random per event.

severity'info' | 'low' | 'medium' | 'high' | 'critical'

Event severity. Omit to pick one at random per event.

action'block' | 'monitor' | 'redact' | 'softBlock' | 'warn'

Enforcement action. Omit to pick one at random per event.

destinationstring

Optional destination (e.g. an AI tool's domain) stored on each event.

countinteger

Number of events to create.

skip_alertsboolean

Store the events without queuing security alert emails.

Response

organization_idstring uuid required
event_idsstring[] required
alerts_queuedinteger required

Alert emails stored for these events, after throttling.

Changes