Sign in

v1

latestOpenAPI 3.0.3FortiCNAPP Use License2026-08-041754351.1 MB
AlertAiAssistant

Continue Alert AI Assistant thread

Continue an existing alert-focused assistant thread. The current public path remains /api/v2/AiAssistants/{threadId}. Follow-up requests must still carry providerConfig plus alert context in conversationContext through either metaInstructions with an alert reference or non-empty entityPayloads. Requests that provide neither are rejected.

put/api/v2/AiAssistants/{threadId}

Path parameters

threadIdstring required

The assistant thread identifier returned by the start request.

Headers

Authorizationstring required

Bearer Access Token. For example, "Bearer {YourAPIToken}"

Content-Typestring required

application/json

Org-Accessboolean

Use this attribute to specify if the access token has organization admin permissions. If the access token has only account permissions, use the Account-Name attribute to specify which account to access.

Account-Namestring

Use this attribute to specify which sub-account to access.

Request body

userQuestionstring required

A follow-up question about the alert context associated with the thread.

assistantTypestring

Optional compatibility field for the existing public route. If supplied, the only supported value is general.

historyobject[]

Optional prior assistant responses for follow-up turns.

Example request

{
  "conversationContext": {
    "metaInstructions": "User is asking about this alert? {alertId:12345}",
    "entityPayloads": [
      {
        "entityKey": "Alert",
        "entityIdentifier": "12345",
        "payloadType": "alert",
        "data": {
          "alertId": 12345
        }
      }
    ]
  }
}

Response

No Error (AI Assistants continue thread)