POST/api/v1/meetings/{meeting_id}/speakers

Name a meeting's speaker

Names a speaker everywhere at once: from is the label as the transcript has it ("Speaker 2", or a name to fix) and to the person's name, or user_id a workspace member (their name is used). The transcript's lines, the Transcript page (written again when nobody edited it, else only each line's speaker), the attendees, the recording's captions, Ask and meeting memory all use the name, and who renamed it is recorded. The summary and Details are written by AI: write them again (POST /api/v1/meetings/{id}/regenerate) to use the names. Returns {renamed: {from, to, lines, transcript, unnamed}, meeting}; transcript is rewritten, updated, left or none. 404 when there's no such speaker, 400 when to isn't a name, 409 when the transcript changed meanwhile. Anyone who can edit the meeting page. 30 a minute.

API token required30 per minute per IPMCP: rename_meeting_speaker

Guide: Name the speakers

Code samples and Try it

Path parameters

#
  • meeting_idstringRequired

Request body

#

application/json, required

  • fromstringRequired

    The speaker label as the transcript has it ("Speaker 2", or a name to fix). 1–120 characters.

  • tostring

    The person's name. Up to 120 characters.

  • user_idstring

    Or a workspace member: their name is used. Up to 40 characters.

Responses

#
  • 200OK.
  • 401No token, or the token is revoked or mistyped.
  • 422The request didn't validate. detail lists each problem, with where it is (loc) and why (msg).
  • 429Too many requests from your IP address. Wait the seconds in Retry-After.
Did this page help?