---
title: "Name a meeting's speaker"
description: "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…"
canonical_url: https://docs.markdrop.in/api/meetings/name-a-meeting-s-speaker
last_updated: 2026-11-20
site: "Markdrop Docs"
index: https://docs.markdrop.in/llms.txt
---

# Name a meeting's speaker

`POST https://api.markdrop.in/api/v1/meetings/{meeting_id}/speakers`

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.

- **Authentication:** API token required: `Authorization: Bearer mdk_…`.
- **Rate limit:** 30 per minute per IP address.
- **MCP tool:** `rename_meeting_speaker` ([tools](https://docs.markdrop.in/ai/tools))
- **Guide:** [Name the speakers](https://docs.markdrop.in/workspaces/meetings#name-the-speakers)

## Path parameters

- `meeting_id` (string, required)

## Request body

`application/json`, required.

- `from` (string, required): The speaker label as the transcript has it ("Speaker 2", or a name to fix). 1–120 characters.
- `to` (string): The person's name. Up to 120 characters.
- `user_id` (string): Or a workspace member: their name is used. Up to 40 characters.

## Responses

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

## Examples

**curl**

```bash
curl -X POST https://api.markdrop.in/api/v1/meetings/MEETING_ID/speakers \
  -H "Authorization: Bearer $MARKDROP_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"from":"Speaker 2","to":"Mayuri Pillay"}'
```

**JavaScript**

```javascript
const res = await fetch("https://api.markdrop.in/api/v1/meetings/MEETING_ID/speakers", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.MARKDROP_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "from": "Speaker 2",
    "to": "Mayuri Pillay"
  }),
});
const data = await res.json();
```

**Python**

```python
import os

import requests

r = requests.post(
    "https://api.markdrop.in/api/v1/meetings/MEETING_ID/speakers",
    headers={"Authorization": f"Bearer {os.environ['MARKDROP_TOKEN']}"},
    json={"from": "Speaker 2", "to": "Mayuri Pillay"},
)
r.raise_for_status()
print(r.json())
```
