---
ref: tool:resend/create-broadcast
name: Create a broadcast
company: company:resend
workflows: []
access: [mcp, cli, api]
tags: [capability:send-email, category:email, has:api, has:cli, has:mcp]
docs: https://resend.com/docs/api-reference/broadcasts/create-broadcast
updated: 2026-09-27
---

# Create a broadcast

Creates a marketing email to every subscribed contact in one segment, saved as a draft or, with send set to true, sent or scheduled at once.

Note: Over MCP it only saves the draft: send it with `send-broadcast`. A draft made without `send` goes out later with `POST /broadcasts/{broadcast_id}/send` or `resend broadcasts send <id>`.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "resend": { "url": "https://mcp.resend.com/mcp" } } }
```

Call the MCP tool `create-broadcast`.

Server URL: https://mcp.resend.com/mcp

### CLI (official)

Install the command, then confirm it runs.

```sh
npm install -g resend-cli
resend --version
```

Run `resend broadcasts create`.

Set `$RESEND_API_KEY` in your environment first (get a key: https://resend.com/api-keys).

### API (official)

- Base URL: https://api.resend.com
- Endpoint: `POST /broadcasts`
- Auth: send the header `Authorization: Bearer $RESEND_API_KEY`
- Get a key: https://resend.com/api-keys
- Docs: https://resend.com/docs/api-reference/introduction

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.