MEmeeting-baas
events

Escalation raised

A representative bot handed a decision back to its owner.

Fires the moment the bot calls its escalate tool, before anyone has answered. Reply with POST /bots/{bot_id}/escalations/{escalation_id}/response and the bot relays the answer to the meeting.

Delivered as an HTTP POST to the bot's callback_url, with the event name in the x-speaking-bot-event header and, when the bot was created with a callback_secret, x-speaking-bot-signature: sha256=<hex>: the HMAC-SHA256 of the exact request body with that secret. Answer with any 2xx. Network errors and 5xx are retried three times (after 1, 3 and 9 seconds); a redirect counts as a failed delivery and is not followed.

postWebhookspeaking_bot.escalation

Payload

event_idstring required

Unique per delivery; use it to drop duplicates

bot_idstring required

The MeetingBaas bot ID returned by POST /bots

client_idstring required

The server's internal ID for the bot

created_atstring date-time required

When the event was produced, ISO 8601 with offset

event'speaking_bot.escalation' required

Response

Received. Any 2xx counts as delivered.

unknown required

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.