---
title: "Escalation Avochato Started"
method: POST
path: "/escalation/avochato/started"
---

# Escalation Avochato Started

`POST /escalation/avochato/started`

## Request

- Base URL: `https://api.palisade.run` (the document declares no server; this is the origin it was published from)
- URL: `https://api.palisade.run/escalation/avochato/started`
- Auth: none declared

Widget pings this after Avochato's iframe transitions to chatting mode
(i.e., the user has submitted the in-iframe form, so a ticket exists).

We look up the AI summary that was stashed when the AI tool fired,
correlate the just-created live-chat ticket via Avochato's REST API
(origin=live-chat + matching IP + recent created_at), and attach the
summary as an agent-only note. Idempotent and best-effort: if the
correlation misses, the agent picks up the chat without the pre-loaded
AI context — not a hard failure.

## Query parameters

- `token` string, nullable

## Headers

- `authorization` string, nullable
- `x-twiddy-chatbot-token` string, nullable

## Request body

- AvochatoStartedRequest
  - `conversation_id` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/palisade-run/apis/twiddy-chatbot-api.md) - [All operations](https://skmtc.dev/palisade-run/apis/twiddy-chatbot-api/llms.txt) - [OpenAPI document](https://skmtc.dev/palisade-run/apis/twiddy-chatbot-api/revisions/80ab7d8068c0?raw)