## Clarify an unclassifiable turn

**post** `/v1/chats/{chat}/clarify`

Asks the customer one clarification question on your behalf, or
escalates when this chat has already used it.

**Behavior**

- No request body.
- Each chat gets one clarification question. A second call escalates
  instead of asking again, and the response's `action` says which
  happened.
- Returns HTTP 202: the question is applied a moment after the response.
- The question runs as a platform flow: the chat's `owner` becomes
  `flow` while it awaits the customer, and your sends during that window
  return HTTP 409 `code` 2011. A rephrase hands the turn straight back
  to you to classify; a reply asking for a person, or five minutes of
  silence, escalates instead. Every ownership movement is recorded by
  `chat.owner_changed`, and the flow's own steps appear on
  `GET /v1/chats/{chat}/events`.

**Errors**

- HTTP 409 `code` 2011: you no longer hold the send turn.

### Path Parameters

- `chat: string`

### Returns

- `action: "clarified" or "escalated"`

  `clarified`: the one bounded question was asked; `escalated`: this chat had already used its question, so we escalated instead.

  - `"clarified"`

  - `"escalated"`

### Example

```http
curl https://messages.api.linqapp.com/v1/chats/$CHAT/clarify \
    -X POST \
    -H "Authorization: Bearer $LINQ_AMB_API_KEY"
```

#### Response

```json
{
  "action": "clarified"
}
```