---
title: "Answer Escalation"
method: POST
path: "/bots/{bot_id}/escalations/{escalation_id}/response"
tags: ["bots"]
---

# Answer Escalation

`POST /bots/{bot_id}/escalations/{escalation_id}/response`

## Request

- Base URL: `https://speaking.meetingbaas.com`
- URL: `https://speaking.meetingbaas.com/bots/{bot_id}/escalations/{escalation_id}/response`
- Auth: API key in header `x-meeting-baas-api-key`
- TypeScript: <https://skmtc.dev/meeting-baas/apis/meeting-baas-api/docs/bots/:bot_id/escalations/:escalation_id/response/post.ts> (a function with typed inputs; its response is checked against the schema)

Answer an escalation the bot raised.

The bot tells the participants the owner's answer, word for word in
substance, and the escalation is marked answered in the briefing. An
escalation that is never answered stays open and is reported as
unresolved; the bot never assumes approval. Only the API key that created
the bot may answer.

## Path parameters

- `bot_id` string, required
- `escalation_id` string, required

## Request body

- EscalationResponseRequest: The owner's answer to an escalation the bot raised.
  - `response` string, required
  - `decision` 'approved' | 'declined' | 'deferred' | 'info', nullable: How the owner decided, when it was a yes/no question

## Response `202`

Queued; the bot relays the answer to the meeting

- AcceptedResponse: The message was queued for the bot.
  - `ok` boolean
  - `message_id` string, required

## Other responses

- `404`: No live bot, or no such escalation
- `422`: Validation Error

## Changes

- **2026-10-30** `e496ccb3de9f`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/meeting-baas/apis/meeting-baas-api/changes/bots/:bot_id/escalations/:escalation_id/response/post.md)

---

[API](https://skmtc.dev/meeting-baas/apis/meeting-baas-api.md) - [All operations](https://skmtc.dev/meeting-baas/apis/meeting-baas-api/llms.txt) - [OpenAPI document](https://skmtc.dev/meeting-baas/apis/meeting-baas-api/revisions/1a4957849576?raw)