resend-cli

Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, and logs via the `resend` CLI. Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates. Always load this skill before running `resend` commands — it contains the non-interactive flag contract and gotchas that prevent silent failures.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "resend-cli" with this command: npx skills add resend/resend-skills/resend-resend-skills-resend-cli

Resend CLI

Installation

Before running any resend commands, check whether the CLI is installed:

resend --version

If the command is not found, install it using one of the methods below:

cURL (macOS / Linux):

curl -fsSL https://resend.com/install.sh | bash

Homebrew (macOS / Linux):

brew install resend/cli/resend

Node.js:

npm install -g resend-cli

PowerShell (Windows):

irm https://resend.com/install.ps1 | iex

After installing, verify:

resend --version

Agent Protocol

The CLI auto-detects non-TTY environments and outputs JSON — no --json flag needed.

Rules for agents:

  • Supply ALL required flags. The CLI will NOT prompt when stdin is not a TTY.
  • Pass --quiet (or -q) to suppress spinners and status messages.
  • Exit 0 = success, 1 = error.
  • Error JSON goes to stderr, success JSON goes to stdout:
    {"error":{"message":"...","code":"..."}}
    
  • Use --api-key or RESEND_API_KEY env var. Never rely on interactive login.
  • All delete/rm commands require --yes in non-interactive mode.

Authentication

Auth resolves: --api-key flag > RESEND_API_KEY env > config file (resend login --key). Use --profile or RESEND_PROFILE for multi-profile.

Global Flags

FlagDescription
--api-key <key>Override API key for this invocation
-p, --profile <name>Select stored profile
--jsonForce JSON output (auto in non-TTY)
-q, --quietSuppress spinners/status (implies --json)

Available Commands

Command GroupWhat it does
emailssend, get, list, batch, cancel, update
emails receivinglist, get, attachments, forward, listen
domainscreate, verify, update, delete, list
logslist, get, open
api-keyscreate, list, delete
broadcastscreate, send, update, delete, list
contactscreate, update, delete, segments, topics
contact-propertiescreate, update, delete, list
segmentscreate, get, list, delete
templatescreate, publish, duplicate, delete, list
topicscreate, update, delete, list
webhookscreate, update, listen, delete, list
authlogin, logout, switch, rename, remove
whoami / doctor / update / openUtility commands

Read the matching reference file for detailed flags and output shapes.

Common Mistakes

#MistakeFix
1Forgetting --yes on delete commandsAll delete/rm subcommands require --yes in non-interactive mode — otherwise the CLI exits with an error
2Not saving webhook signing_secretwebhooks create shows the secret once only — it cannot be retrieved later. Capture it from command output immediately
3Omitting --quiet in CIWithout -q, spinners and status text leak into stdout. Use -q to get clean JSON only
4Using --scheduled-at with batchBatch sending does not support scheduled_at — use single emails send instead
5Expecting domains list to include DNS recordsList returns summaries only — use domains get <id> for the full records[] array
6Sending a dashboard-created broadcast via CLIOnly API-created broadcasts can be sent with broadcasts send — dashboard broadcasts must be sent from the dashboard
7Passing --events to webhooks update expecting additive behavior--events replaces the entire subscription list — always pass the complete set
8Expecting logs list to include request/response bodiesList returns summary fields only — use logs get <id> for full request_body and response_body

Common Patterns

Send an email:

resend emails send --from "you@domain.com" --to user@example.com --subject "Hello" --text "Body"

Send a React Email template (.tsx):

resend emails send --from "you@domain.com" --to user@example.com --subject "Welcome" --react-email ./emails/welcome.tsx

Domain setup flow:

resend domains create --name example.com --region us-east-1
# Configure DNS records from output, then:
resend domains verify <domain-id>
resend domains get <domain-id>  # check status

Create and send a broadcast:

resend broadcasts create --from "news@domain.com" --subject "Update" --segment-id <id> --html "<h1>Hi</h1>" --send

CI/CD (no login needed):

RESEND_API_KEY=re_xxx resend emails send --from ... --to ... --subject ... --text ...

Check environment health:

resend doctor -q

When to Load References

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

resend

No summary provided by upstream source.

Repository SourceNeeds Review
4.6K-resend
General

email-best-practices

No summary provided by upstream source.

Repository SourceNeeds Review
4.4K-resend
General

react-email

No summary provided by upstream source.

Repository SourceNeeds Review
3.6K-resend
Automation

agent-email-inbox

No summary provided by upstream source.

Repository SourceNeeds Review
858-resend