---
title: "Bot recording completed"
method: POST
path: "bot.recording_completed"
tags: ["Bots"]
---

# Bot recording completed

`POST bot.recording_completed` (webhook)

Sent when the provider recording is available for processing. The
transcript and summary are not ready yet.

Delivered to every workspace webhook endpoint subscribed to this event,
signed with the endpoint's `whsec_` secret. See
[Webhooks](/api-reference/webhooks#verification-code) for signature verification, retries,
and ordering.

## Payload

- BotEvent
  - `id` string: Stable typed event ID beginning with `evt_`. Use it to deduplicate retries.
  - `type` 'bot.recording_started' | 'bot.recording_completed' | 'bot.transcript_ready' | 'bot.summary_ready' | 'bot.failed' | 'bot.cancelled': The event type. Also sent in the `X-HappyScribe-Event` header. - `bot.recording_started`: the notetaker is in the call and recording. - `bot.recording_completed`: the call ended and the recording is available. - `bot.transcript_ready`: the transcript is ready. - `bot.summary_ready`: the summary is ready; the bot is `completed`. - `bot.failed`: the bot ended without a usable result. - `bot.cancelled`: the bot was cancelled.
  - `created_at` string, date-time: When HappyScribe emitted the event.
  - `data` object: `object`: the bot, as `GET /bots/{id}` returns it.
    - `object` Bot: A bot is one way of recording a meeting. It carries its identity in the call and the meeting's recording choices; what the meeting produced (transcript, speakers, summary, media) is read from [`GET /meetings/{id}/results`](/api-reference/meetings/results).
      - `id` string: Stable typed bot ID beginning with `bot_`. Treat it as an opaque string.
      - `object` string: Always `bot`.
      - `meeting_id` string: The meeting this bot records, beginning with `mtg_`. It exists from the moment the bot is queued; read its results with `GET /meetings/{meeting_id}/results`.
      - `meeting_url` string: Normalized URL supplied at creation. Treat as sensitive — it may contain credentials.
      - `join_at` string, date-time, nullable: Requested ISO 8601 join time, or `null` for an immediate dispatch.
      - `status` 'queued' | 'joining' | 'in_call' | 'processing' | 'completed' | 'failed' | 'cancelled': Current lifecycle state: - `queued`: the provider accepted the bot and the notetaker is pending - `joining`: the notetaker is joining the call - `in_call`: the notetaker is in the call and recording - `processing`: the recording is being transcribed or summarized - `completed`: the transcript and summary are ready on the meeting - `failed`: the bot ended without a usable result - `cancelled`: the bot was cancelled
      - `bot_name` string: Display name of the notetaker in the call.
      - `welcome_message` string, nullable: Chat message the notetaker posts when it joins, or `null` when it posts none.
      - `language` string: Transcription language as a BCP-47 code, `auto` or `multi`. The meeting's `effective_policy.transcription.language`.
      - `recording_start` 'on_join' | 'on_command': When the notetaker starts recording. The meeting's `effective_policy.recording.methods.bot.start`. - `on_join`: as soon as it joins the call - `on_command`: when someone in the call asks it to
      - `recording_mode` 'audio_and_video' | 'audio_only': What the notetaker records. The meeting's `effective_policy.recording.methods.bot.mode`. - `audio_and_video`: audio and video - `audio_only`: audio only
      - `silence_alert` boolean: Whether the notetaker posts an audible and chat alert after a long silence, in case it is recording nothing. The meeting's `effective_policy.recording.methods.bot.silence_detection.alert`.
      - `summary_language` string, nullable: Language of the summary as a BCP-47 code, or `null` to follow the transcription. The meeting's `effective_policy.summary.language`.
      - `summary_template` string, nullable: The summary template that runs, a built-in slug or a custom template's `tpl_` id. The meeting's `effective_policy.summary.template`.
      - `participants` MeetingParticipant[]: Everyone invited to the meeting. Meeting rooms and the notetaker itself are excluded.
        - `email` string: The participant's email. Used to name speakers.
        - `name` string, nullable: Resolved from the calendar invite, anything supplied at creation, the names people displayed in the call, and the people the workspace already knows, keeping the fullest. Null when no source knew one.
      - `metadata` Metadata: Your own key-value pairs, for your ids and context. HappyScribe stores them, returns them on the object and in every webhook that carries it, and never acts on them. Up to 50 keys of up to 40 characters (no square brackets), values up to 500 characters. See [metadata](/meetingkit/setup#a-workspace-per-customer).
      - `created_at` string, date-time: When the bot was created.
      - `ended_at` string, date-time, nullable: When the recording first became available. `null` until then, and for a bot that never recorded. Reprocessing does not change it.
      - `reason` 'no_recording' | 'invalid_meeting_url' | 'bot_error' | 'transcription_failed': Machine-readable failure reason. Present only for failed bots. - `no_recording`: the call ended without anything recorded - `invalid_meeting_url`: the meeting URL could not be joined - `bot_error`: the notetaker failed in the call - `transcription_failed`: the recording could not be transcribed
      - `failure_message` string, nullable: Human-readable failure detail for debugging. Present only for failed bots. Do not match on its text; use `reason`.

## Acknowledgement `200`

Return any 2xx status to acknowledge receipt. Any other status, or a timeout, triggers a retry — up to 21 attempts with backoff.

---

[API](https://skmtc.dev/happyscribe/apis/happyscribe-api.md) - [All operations](https://skmtc.dev/happyscribe/apis/happyscribe-api/llms.txt) - [OpenAPI document](https://skmtc.dev/happyscribe/apis/happyscribe-api/revisions/1281bd968c3d?raw)