Resend Release Notes

Retrieve your account usage and plan limits directly from the API.

Today, we're introducing the Usage API. One request returns your current usage and limits across every quota on your account.

What you can build with it

• Quota alerts: notify your team before you hit your daily or monthly email limit.
• Send throttling: pause non-critical sends when you're close to a cap.
• Internal dashboards: show Resend usage next to your infrastructure metrics.
• Agent awareness: let your agent check remaining quota.

Retrieving your usage

Call GET /usage with a full access API key.

What's in the response

The response covers every quota on your account:

• emails: sent and received emails, viewable by daily or monthly windows.
• contacts: how many contacts have been used from your quota.
• segments: how many segments have been used from your quota (if applicable).
• broadcasts: how many total broadcasts have been created.
• domains: how many domains have been used from your quota (if applicable).
• ai_credits: credits used along with next_increase_at.
• automation_runs: runs used this period and when the count resets.
• rate_limit: your team's API rate limit for all requests.

A limit of null means there's no cap for that resource on your plan.

Available in the CLI and MCP server

Run resend usage in the CLI to see a table of your usage, or resend usage --json for scripts. The MCP server also includes a get-usage tool, so your agent can check your limits on its own.

To learn more, check out the API documentation.

Original source

Duplicate an existing broadcast directly from the API.

Most new Broadcasts start from one you've already sent. Previously, duplicating a Broadcast was only possible from the Dashboard.

Today we're releasing a new API endpoint to duplicate a broadcast.

How it works

Pass the ID of an existing Broadcast and the API creates a copy:

• The copy is named after the original with a (copy) suffix, truncated to 70 characters.
• The segment, topic, sender, subject, reply-to, preview text, and content are copied.
• The copy starts as a draft. Nothing is sent until you review and send it.

Any Broadcast can be duplicated, including ones that have already been sent.

Duplicating a Broadcast

To duplicate a Broadcast, use the Broadcast's ID with the duplicate endpoint.

import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

const { data, error } = await resend.broadcasts.duplicate(
  '559ac32e-9ef5-46fb-82a1-b76b840c0f7b',
);

The endpoint returns the ID of the new Broadcast:

{
  "object": "broadcast",
  "id": "1f85ae38-f5b9-4c1f-8766-667a53970fea"
}

The duplicate Broadcast API is part of a larger move to bring the full functionality of the dashboard into the API, CLI, and MCP, so you can build how you want.

If you have any questions, please reach out to us and we'll be happy to help.

Original source

Build custom headless webhook experiences from the API, SDKs, CLI, and MCP server.

Today, we're introducing the Headless Webhook API. Everything the webhook detail page does is now available in the API, every SDK, the CLI, and the MCP server:

• List Events: every event delivered to a webhook, with its delivery status.
• Retrieve Event: the exact payload we sent to your endpoint.
• List Attempts: list all attempts with the status code and body your endpoint returned.
• Replay Event: queue another delivery of a webhook event.
• Rotate Signing Secret: get a new secret without opening the dashboard.

What you can build with it

• Automated recovery: list failed events on a webhook and replay them in a loop.
• Delivery alerts: poll for failed events and page your team before customers notice.
• Secret rotation on a schedule: rotate signing secrets from your secrets manager or CI.
• Agent-driven debugging: connect the MCP server and ask your agent what failed.

Find what failed

List the events delivered to a webhook. Each one carries the delivery status for that endpoint: success, failed, attempting, or pending.

Events come back most recent first and paginate forward with after. Only events inside your plan's data retention window are returned.

Inspect the payload

Retrieve Event gives you the exact payload we sent and when the next automatic retry is scheduled.

The payload is exactly what your endpoint received, so you can replay it locally against your handler.

See what your endpoint returned

List Attempts shows what happened each time we tried, so you can tell a timeout from a 500 without digging through your own logs.

Each attempt carries the status code and response body your endpoint returned.

Replay it

Once your endpoint is healthy again, replay the event. This is the same action as the Replay button in the dashboard.

A replay queues one delivery right away and doesn't change the automatic retry schedule already running for that event. The webhook must be enabled. If we auto-disabled it after repeated failures, re-enable it first, then replay.

Rotate the signing secret

If a signing secret leaks, or you rotate secrets as routine hygiene, you no longer need the dashboard to do it.

The response includes the new secret, so there's no second request.

For 24 hours after rotating, payloads are signed with both the previous and the new secret, so you can roll out the new one to your handler without dropping events. Learn more about verifying webhook requests.

Conclusion

These endpoints are part of a larger move to bring the full functionality of the dashboard into the API, CLI, and MCP server.

If you have any questions, please reach out to us and we'll be happy to help.

Original source

Retrieve the links clicked in a broadcast

Today we are releasing a new API endpoint to retrieve the links clicked in a broadcast. It returns every link clicked in a broadcast, ranked by total clicks.

To view the click rates for your emails you will need to enable click tracking for your domain.

What you can build with it

• Your own dashboard: connect other sources of data to understand how your subscribers interact with your emails
• Cross-campaign reports: identify which URLs and CTAs drive the most engagement across your broadcasts
• Optimized content strategies: surface your top-performing links to inform future email design and messaging

Retrieving link clicks

Use the ID of any broadcast. The API returns a list of every link in the broadcast that was clicked and their total and unique clicks, sorted by total clicks.

The response looks like this:

{
  "object": "list",
  "has_more": true,
  "data": [
    {
      "id": "b2Zmc2V0OjA",
      "url": "https://resend.com/pricing",
      "clicks": 42,
      "unique_clicks": 30
    },
    {
      "id": "b2Zmc2V0OjE",
      "url": "https://resend.com/docs",
      "clicks": 17,
      "unique_clicks": 15
    }
  ]
}

You can also retrieve the link clicks in the Resend CLI and through the MCP server, so your agents can help you understand how your emails are performing.

Original source

Add beautiful tables to your Broadcasts and Templates.

Data is often much easier to scan when it's visual.

• Order receipts: line items, quantities, and totals
• Plan comparisons: features and prices side by side across tiers
• Event schedules: sessions, times, and locations

Today, we're introducing a Table component in the Broadcast and Template editors.

How it works

Type /table or pick Table from the component toolbar to insert a 3x3 table.

Make continued adjustments to fit your needs:

• Rows and columns: add or delete them from the row and column menus, or press Tab in the last cell to add a row.
• Headers: toggle a header row or header column.
• Alignment: align each column left, center, or right.
• Style: choose all borders, horizontal borders, or none, and turn on striped rows.

Cells hold text, images, and variables, so a table can pull in contact properties like everything else in the editor.

Paste Markdown tables

If you already keep a table in Markdown, paste it straight into the editor. It becomes a Table component, and the alignment markers in the separator row carry over to each column.

Plan Seats Price Starter 1 $0 Pro 5 $20 Team 25 $80

The first column stays left-aligned, seats are centered, and prices are right-aligned, exactly as written.

Send a test email first

Email clients each render tables a little differently. Before you send to your audience, click Test email in the editor and check how the table looks in your own inbox.

What else do you want us to add to the editor? Let us know how we can make the editor experience even better for you.

Original source

Add Resend email to your v0 projects without leaving v0.

Today, we're excited to announce the Vercel v0 Integration. Add email to your v0 project with Resend without handling API keys or managing DNS records.

Many builders create projects using Vercel's v0 platform. The new integration makes it easy to integrate email with Resend without leaving your v0 workflow.

Email for developers, easier to integrate than ever.

What's new

• Create a new Resend account directly from your v0 project
• A Resend API key is added to your v0 project's environment variables
• DNS for Resend is automatically configured through v0
• Billing is managed through v0

Prerequisites

Before you begin, you'll need two things:

• A Vercel v0 account with a project.
• A domain purchased through Vercel.

How to get started

The integration connects Resend to your v0 project using your Vercel domain.

1. Ask v0 to add email to your application

You can ask v0 something like:

Add an email capture to my application using Resend. Store the user's email as a Contact in Resend and send them a welcome email.

v0 will show a prompt to install Resend in your project.

This will take you to the integration page, where you can follow the instructions to add email to your project.

2. Finish setup

Follow the "finish setup" link to view your v0 domain in the Resend dashboard.

It can take a few minutes for the DNS records to propagate. Once they have, you can return to v0 and let it know you're ready to start sending emails.

By default, v0 will use a from address of [email protected]. This address is only for testing purposes, and will not send to anyone but yourself. To send to your users, tell v0 to use a from email address connected to the domain you just set up.

My domain is verified. Please send emails from [email protected].

Now you're ready to send and receive emails with Resend.

Empowering developers

Our goal is to empower developers to ship quickly with confidence, taking care of the busy work so they can get back to building the projects they love.

This new integration makes it even easier for v0 users to get started with Resend, and we can’t wait to see what you do with it.

Original source

Catch broken, missing, and placeholder links before you send a Broadcast or publish a Template.

A broken link is easy to miss in the editor and hard to take back once an email is sent.

Today, we're introducing a link checker in the Broadcast and Template editors so you can catch issues before you send.

When you send a Broadcast or publish a Template, Resend checks the links in your email and flags:

• Broken links that return a 404 or other error
• Missing or invalid URLs, like empty buttons
• Placeholder links, such as example.com or TODO destinations
• Anchor links (#...), which don't work in most email clients

Click any issue to jump to it in the editor and fix it before you send.

What other custom components would you like us to add? Reach out and let us know!

Original source

Let your team sign in to Resend with your identity provider.

Today, we're adding Single Sign-On (SSO) to Resend.

Once it's set up, anyone with an email address on your organization's domain can log in to your Resend team through your identity provider (IdP), no invite required.

SSO is available as an add-on to Scale plans and included with an Enterprise plan.

SSO options

By default, enabling SSO adds a new way for users to log in to your team, although you can enable two additional options:

• Enforced: users can only sign in through your IdP, and removing a user from the IdP removes them from your Resend team.
• Restricted: users on your SSO domain cannot create new teams, be invited to, or accept invitations from teams outside your SSO organization. Contact support to enable this for your domain.

Set SSO up

There are a few steps to set up SSO. First, you must be an Admin of your team and use an email address from the domain you want to use for SSO. Follow these steps:

• Navigate to your Team Settings and click Enable SSO.
• Enter your organization domain: this is the domain your team members use to log in, it doesn't have to match any domains you have set up to send or receive email.
• Verify your domain: add a TXT record at the apex of your domain; the unique value will be shown on your dashboard. If it's already verified for sending, this step is skipped.
• Wait for verification: Resend polls your DNS until it finds the TXT record.
• Connect your IdP: back in Team Settings click on Finish setup. A new tab opens where you configure the connection to your IdP.

Anyone who signs in through SSO and isn't yet a member of the team is added automatically with the Member role.

Conclusion

SSO gives your team one place to manage who can access Resend, and one place to cut that access off. For the full setup walkthrough and troubleshooting, see the SSO docs.

If you have any questions, please reach out to us and we'll be happy to help.

Original source

Rename an existing API key from the API without regenerating its token.

Today we're introducing PATCH /api-keys/:id to rename an API key in place. The token stays the same, and so do the key's permission and domain restriction.

What you can build with it

• Provisioning workflows: keep key names in sync when a project gets renamed.
• Naming convention cleanups: rename every key from a script without rotating secrets.
• Platform integrations: let your users rename the keys your app provisions for them.

Renaming a key

Send the new name (up to 50 characters) with the ID of the key you want to rename.

import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

const { data, error } = await resend.apiKeys.update(
  'b6d24b8e-af0b-4c3c-be0c-359bbd97381e',
  {
    name: 'Production'
  },
);

The response confirms the rename:

{
  "object": "api_key",
  "id": "b6d24b8e-af0b-4c3c-be0c-359bbd97381e"
}

This endpoint only updates the name. To change a key's permission or domain restriction, edit the key in the Resend Dashboard.

Conclusion

Renaming keys is also available in the Resend CLI and through the MCP server, so your agents can tidy up key names too.

Original source

Create a shareable link to view a sent or received email directly from the API.

Today we're releasing a new API endpoint to share an email. It returns a link to a read-only view of any sent or received email, viewable by anyone with the link.

Share any email with someone outside of your team, like when a:

• client wants confirmation an email was sent
• teammate without dashboard access needs to see an email
• support tool needs a quick preview

You can already create a shareable link from the dashboard, and now also from code.

What you can build with it

• Support tooling: attach a live email preview to a ticket.
• Customer-facing history: let users open a "view this email" link from your app.
• Agent workflows: ask your agent to surface the email when reporting on a send.
• Debugging with your team: share a link to see the email when investigating issues.

Creating a share link

Use the ID of any sent or received email. The API returns the full share URL.

The response includes the link, ready to hand off:

{
  "object": "email",
  "id": "49a3999c-0ce1-4ea6-ab68-afcd6dc2e794",
  "url": "https://resend.com/shared?token=eyJhbGciOiJIUzI1NiJ9..."
}

How expiration works

Share links are temporary by design. Anyone with the link can view the email while it's still active, but links always expire.

• expires_in accepts a human-readable duration like 10m, 2 hours, or 1 day.
• If you don't pass it, the link lasts 48 hours, which is also the maximum.
• Invalid or over-limit durations return a validation error.

Conclusion

The share email API is part of a larger move to bring the full functionality of the dashboard into the API. You can also create share links from the Resend CLI or delegate it to your agent through the MCP server.

Original source

Get deliverability and engagement metrics through the new Email Metrics API.

Today we are releasing the new Email Metrics API.

Get data about your emails, from the send volume to unsubscribe rate, grouped or filtered by the period, domain, broadcast, or email.

This data enables you to build:

• custom dashboards showing your deliverability and reputation metrics
• reports that summarize campaign performance
• alerts to notify you if bounce or complaint rates spike

Try hooking your agent up to the Resend MCP server and asking:

Chart our sender reputation risk over the last 30 days: bounce rate, unsubscribe rate, and complaint rate as percentages of delivered. Flag if any metric crossed the Gmail/Yahoo thresholds.

Your agent will build out a custom dashboard showing you those deliverability metrics plotted against industry thresholds.

How it works

A new API endpoint is available: /emails/metrics.

Making a request with no parameters returns all metrics for all of your emails over the past 7 days.

The response will look like this, with the totals for each metric over the period.

Filtering and grouping

There are three components to the metrics API:

• filters (start_date, end_date, timezone): these help you restrict the time period over which the metrics are returned. The start_date can go back as far as your account retains data.
• metrics: these are the numbers you want to see. By default the API returns all the metrics available, but you can restrict the metrics returned. For example, to retrieve the open and click rate only, pass metrics=opened,clicked.
• dimensions: these are ways to group the metrics. For example, you can group by period, then set the granularity to "hourly" and you would see a group of metrics for each hour in the period.

Read more about the available parameters in the Email Metrics API documentation.

To list the sent and delivered metrics for each domain over the last day, broken down by hour like this, make a request like:

When you choose dimensions to partition the data, the data array shows each group. For instance, in the example response below the data is grouped by both domain and hour because the dimensions "period" and "domain" were selected and the granularity was set to "hourly".

These metrics APIs are part of a larger move to bring the full functionality of the dashboard into the API, CLI, and MCP, so you can build how you want or experience the data through your agent.

Original source

Install the MCP server and every Resend skill directly from the Cursor Marketplace.

The best agent experience requires context provided by tooling like MCP servers, skills, and CLIs. Historically, getting the most out of Cursor with Resend meant installing the MCP server and every skill separately.

Today, we're excited to announce the official Resend plugin for Cursor. The plugin bundles the MCP server and every Resend Skill into a single install.

What you can do with it

• Send from a conversation: send a transactional email without leaving Cursor.
• Debug deliverability: pull up logs, inspect a bounce, or check why an email failed.
• Manage Contacts and Segments: add contacts, build segments, and clean up email lists in plain language.
• Run Broadcasts: draft, schedule, and send a broadcast to an audience.
• Check Domains and API Keys: verify domain status, review DNS records, and rotate API keys.

How to use it

To install the plugin, open Cursor and run:

/add-plugin resend

You can also browse the Cursor Marketplace, or open Customize in the sidebar, search for Resend, and select Install.

After install, sign in with your Resend account when Cursor prompts you to authenticate the MCP server.

Email expertise, on by default

Once installed, Cursor activates the right skill automatically:

• resend for the SDK and platform APIs
• react-email for building templates as React components
• email-best-practices for SPF, DKIM, DMARC, compliance, and deliverability
• agent-email-inbox for safely processing inbound email with an agent
• resend-cli for shell and CI workflows

The MCP server (or Resend CLI) lets Cursor perform actions like sending emails, managing templates, and processing inbound email. Skills ensure the tooling follows best practices in a token-efficient way.

Conclusion

We're excited to see how this connection makes it easier to build with Resend and Cursor. Head to the Cursor page for everything Resend brings to your agent.

If you have any questions, please reach out to us and we'll be happy to help.

Original source

Duplicate an existing automation directly from the API.

Most new automations start from one that already works. Previously, duplicating an Automation was only possible from the Dashboard.

Today we're releasing a new API endpoint to duplicate an automation.

How it works

Pass the ID of an existing Automation and the API creates a copy:

• The copy is named after the original with a (Copy) suffix.
• All steps and connections are copied from the currently published version, or from the most recent version if none is published.
• The copy starts as a disabled draft. Nothing runs until you review and publish it.

Duplicating an Automation

To duplicate an Automation, use the Automation's ID with the duplicate endpoint.

import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

const { data, error } = await resend.automations.duplicate(
  'c9b16d4f-ba6c-4e2e-b044-6bf4404e57fd',
);

The endpoint returns the ID of the new Automation:

{
  "object": "automation",
  "id": "e169aa45-1ecf-4183-9955-b1499d5701d3"
}

The duplicate Automation API is part of a larger move to bring the full functionality of the dashboard into the API, CLI, and MCP, so you can build how you want.

If you have any questions, please reach out to us and we'll be happy to help.

Original source

The free tier now includes 3 verified domains, so you can build and send from more projects without upgrading.

Since our beginning, the free tier has included a single verified domain, a limitation that works for one project, but limits you even as you try to follow our best practices.

Today, we're increasing the free tier to three domains. Every free team can now verify up to three domains, in any region, at no cost.

What you can build with it

• More side projects: give each product its own domain without needing to upgrade.
• Separate sending subdomains: keep transactional email on one domain and marketing on another to protect your deliverability.
• A real staging environment: verify a staging domain and test changes safely before they reach your users.

Add your next domain

You can add a domain from the Domains page in the dashboard.

Of course you can also add domains via the CLI, MCP, or API as well.

import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

const { data, error } = await resend.domains.create({ name: 'example.com' });

Conclusion

The new limit is live today for every free team. Your team's quotas are shared automatically across all domains.

View our pricing page for full details.

Original source