Сажети опис тикета

Show/Trigger

Required permission: ticket.agent

POST-Request sent: /api/v1/tickets/{ticket id}/summarize

The ticket summarize endpoint uses POST because creating and fetching the summary happen in a single operation:

If a summary exists, it is returned.
If a summary does not exist, creation is triggered in the background (async job).

Using GET would be incorrect since the call may also create data. If you want a summary to exist, call the endpoint; if it's not ready yet, retry after at least 30 seconds.

Sample response if the generation of a new summary was just triggered by the request:

Details

json

// HTTP Code 200 Ok

{
  "result": null
}

Sample response for an existing summary (e.g. for the same ticket like above after waiting until creation has finished):

Details

json

// HTTP Code 200 Ok

{
  "result": {
    "language": "en-US",
    "customer_mood": "concerned",
    "open_questions": [
      "Can you please tell us what color the LED is flashing and how often it flashes?"
    ],
    "upcoming_events": [],
    "customer_emotion": "😐",
    "customer_request": "Laptop not working [Order 931529477]",
    "conversation_summary": "Customer Petra Parker reports a problem with her customized laptop, which only flashes one LED when pressed. Agent Alexander Jensen asks for more details and clarifies the issue with 2nd level support.",
    "fingerprint_md5": "e516dda67c26605f31ea5ea9f8b184cf",
    "relevant_for_current_user": true
  }
}

Сажети опис тикета ​

Show/Trigger ​

Сажети опис тикета

Show/Trigger