> ## Documentation Index
> Fetch the complete documentation index at: https://developer.z-api.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Update broadcast list

> Updates an existing broadcast list

## Overview

This method allows you to update an existing broadcast list, changing its name and/or the numbers it contains.

<Warning>
  Please be aware of the limitations and rules around the use of broadcast lists. For more details, check the [introduction](/en/broadcast/introduction).
</Warning>

***

## Attributes

### Header

<ParamField path="instanceId" type="string" required>
  Your instance ID. Available in the Z-API panel under **Instances**.
</ParamField>

<ParamField path="token" type="string" required>
  Your Z-API instance token.
</ParamField>

### Path

<ParamField path="broadcastId" type="string" required>
  ID of the broadcast list to be updated. Ex: 1779474934\@broadcast
</ParamField>

### Optional

<ParamField body="name" type="string">
  New name for the broadcast list
</ParamField>

### Required

<ParamField body="phones" type="array" required>
  Full list of recipient numbers in E.164 format without `+`. Ex: 5511999999999
</ParamField>

<Info>
  The `phones` field **completely replaces the current list** on every request. Therefore:

  * To **add** a contact, send all existing numbers along with the new one.
  * To **remove** a contact, send all existing numbers, omitting only the ones you want to remove.
</Info>

***

## Request Body

```json theme={"theme":{"light":"github-light","dark":"poimandres"}}
{
  "name": "List name",
  "phones": ["5511999999999", "5511888888888"]
}
```

***

## Response

### 200

```json theme={"theme":{"light":"github-light","dark":"poimandres"}}
{
  "broadcastId": "1778158856@broadcast",
  "name": "Updated broadcast list",
  "phones": [
    "5511999999999",
    "5511888888888",
    "5511777777777"
  ]
}
```

### 405

Make sure you are sending the request with the correct HTTP method. Check that you are using PUT as specified at the top of this page.

### 415

If you receive a 415 error, make sure to include the `Content-Type` header in your request. In most cases, the value should be `application/json`.