TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/samkit511/SAW---Security-Analyst-Workspace/llms.txt
Use this file to discover all available pages before exploring further.
/assistant/request endpoint supports three request_type values: log_triage (covered in the log ingestion guide), incident_followup, and task_command. The last two let you re-engage the assistant pipeline against an incident that already exists, and give you a conversational interface for managing tasks without calling the /tasks endpoints directly. Both types benefit from the optional session_id field, which links requests into a continuous session so the assistant can maintain context across turns.
incident_followup
Useincident_followup to ask the assistant to re-analyze an existing incident, produce updated recommendations, and generate additional follow-up tasks. SAW reuses the stored classification from the original triage run rather than re-running the full pipeline from scratch.
Required payload fields
| Field | Type | Description |
|---|---|---|
incident_id | string | The incident_id returned from the original triage request |
message | string | Analyst question or instruction for the assistant |
source | string | Label for the originating surface (e.g. analyst_console) |
agent_summary, any new tasks created by the follow-up run, and the same request_id / incident_id / workflow_status structure as a triage response:
The
incident_id in the payload must match an incident that SAW has already stored. If you pass an unknown ID, the assistant will return an error or produce a degraded response with no stored context to work from.task_command
Usetask_command when you want to manage tasks through the assistant interface instead of calling /tasks directly. The action field in the payload controls which operation runs.
- create
- list
- complete
Create a new task linked to an incident:
task_command payload fields
| Field | Type | Required for | Description |
|---|---|---|---|
action | string | all | create, list, or complete |
title | string | create | Task title |
description | string | create | Task description |
incident_id | string | create, list | Incident to associate or filter by |
priority | string | create | LOW, MEDIUM, or HIGH |
task_id | string | complete | ID of the task to mark complete |
Session continuity
Bothincident_followup and task_command accept a session_id string. Pass the same value across multiple requests to link them into a session. The assistant uses the session context to maintain awareness of prior turns — for example, referencing tasks created earlier in the same session without you re-supplying their IDs.
session_id or set it to null if you want each request to be treated as an independent, stateless call.