---
ref: tool:resend/send-event
name: Send an event
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/events/send-event
updated: 2026-09-27
---

# Send an event

Sends a named event for one contact, by contact ID or email address, and starts every automation that event triggers.

Pass exactly one of `contact_id` or `email`; an email address with no contact
yet becomes one when the automation runs. The optional `payload` feeds the
automation's template variables and conditions, and is checked against the
event's schema when it has one.

## 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 `send-event`.

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 events send`.

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 /events/send`
- 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 doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.