Resend Release Notes

Follow

23 release notes curated from 25 sources by the Releasebot Team. Last updated: Nov 5, 2026

Get this feed:
  • Nov 4, 2026
    • Date parsed from source:
      Nov 4, 2026
    • First seen by Releasebot:
      Nov 5, 2026
    Resend logo

    Resend

    TruffleHog Secrets Revocation Program

    Resend now automatically revokes exposed live API keys found across public code, packages, container images, and datasets through its TruffleHog partnership, notifying account admins. The default-on protection expands detection beyond GitHub to help limit abuse and protect sending reputations.

    Live Resend API keys found in Docker images, Hugging Face datasets, and other public sources are now revoked automatically.

    In July, we became a GitHub secret scanning partner. Any Resend key exposed on public GitHub is revoked automatically.

    GitHub's program covers public GitHub repositories and npm, and yet many keys leak in other locations like Docker images, packages, other registries, and public datasets.

    Today, we're announcing that Resend is a launch partner in TruffleHog's Secrets Revocation Program. TruffleHog scans public code, packages, container images, and datasets for exposed keys. When it finds a working Resend key, it reports it to us and we revoke it automatically.

    Where TruffleHog looks

    TruffleHog adds another route for finding exposed keys across:

    • Docker Hub images
    • Hugging Face datasets
    • PyPI and npm packages
    • GitLab repositories
    • Android apps and Firefox add-ons
    • New pushes to GitHub

    What happens when a key leaks

    1. Verified as live: TruffleHog tests every key it finds and reports keys that still work.
    2. Revoked automatically: We disable the exposed key as soon as the report arrives.
    3. Your team is notified: We email all admins with a link to where the key was found.

    This security protection is on by default for every Resend account.

    Why we revoke instead of warn

    TruffleHog found that 81% of the leaked keys it reported last year were still live six months later. A warning email leaves the key working until someone acts on it.

    For email, a live leaked key means anyone can send spam or phishing from your verified domain, endangering your recipients and your sending reputation. If the leak endangers your sending reputation, it can take weeks to rebuild.

    To protect you and your recipients, revoking the key immediately closes that window.

    Conclusion

    Between GitHub and TruffleHog, a leaked Resend key gets caught in far more places than before, and it's revoked before it can hurt your sending reputation. View the TruffleHog announcement post for more details on the program.

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

    Original source
  • Oct 26, 2026
    • Date parsed from source:
      Oct 26, 2026
    • First seen by Releasebot:
      Oct 26, 2026
    Resend logo

    Resend

    Support for AI Catalog and MCP Server Card

    Resend now lets compatible MCP clients discover and configure its MCP server from one URL using public AI Catalog and MCP Server Card documents, while retaining OAuth or API-key sign-in and direct endpoint access for other clients.

    MCP clients can now find and configure the Resend MCP server from a single URL.

    Adding an MCP server to a client usually means digging through docs for the right endpoint, transport, and auth setup. Resend now publishes an AI Catalog and an MCP Server Card, so supporting clients can discover the Resend MCP server from just a URL.

    How discovery works

    Both files are public, static JSON documents any client can read before connecting:

    • AI Catalog at resend.com/.well-known/ai-catalog.json lists the AI artifacts Resend offers, including the remote MCP server.
    • MCP Server Card at mcp.resend.com/mcp/server-card describes the server's name, Streamable HTTP endpoint, and supported protocol versions.

    Give a client that supports these discovery methods resend.com, and it reads the AI Catalog, follows the entry to the Server Card, and connects. You still sign in with OAuth, or pass a Resend API key as a Bearer token for headless setups.

    Built on open standards

    The AI Catalog format is maintained by the Agent Card Working Group under the Linux Foundation. MCP Server Cards are defined in SEP-2127, an official MCP extension.

    Get started

    If your client supports Server Card discovery, add resend.com as an MCP server and follow the sign-in prompt. For every other client, the server is hosted at https://mcp.resend.com/mcp.

    For more installation options, see the MCP server documentation.

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Resend and hundreds of other software products.

    Create account
  • Oct 19, 2026
    • Date parsed from source:
      Oct 19, 2026
    • First seen by Releasebot:
      Oct 21, 2026
    Resend logo

    Resend

    Compress and Convert Images in the Editor

    Resend now automatically compresses large images and converts unsupported formats in its Broadcast and Template editors before upload, making images email-ready without manual resizing. GIF animations stay intact, and transparency is preserved when images are converted to PNG.

    Automatically compress large images and convert WebP, HEIC, SVG, and more.

    Starting today, the Broadcast and Template editors automatically:

    • compress large images
    • convert unsupported formats

    These improvements happen before upload. Drop, paste, or pick any image and the editor prepares it for email.

    Automatic compression

    Email clients render most emails around 600px wide, so a full-resolution photo requires every recipient to download a larger image for no benefit.

    • Images over 1 MB are resized to a maximum of 1500px wide and re-encoded.
    • GIFs are never compressed, so animations stay intact.

    Lighter images load faster for your recipients and keep your emails smaller.

    Format conversion

    Email clients reliably support JPEG, PNG, and GIF. Other formats are not commonly supported, so they are now converted in the browser before upload:

    • SVG
    • WebP and AVIF
    • HEIC and HEIF (photos from iPhone)
    • BMP, ICO, and TIFF (TIFF only in browsers that can read it)

    Images with transparency become PNG, so logos and cut-outs keep their transparent background. Everything else becomes JPEG. Converted images are also resized to a maximum of 1500px wide, whatever their file size.

    Conclusion

    You no longer need to resize or convert images before adding them to an email.

    If you have any questions, view our documentation or reach out to us and we'll be happy to help.

    Original source
  • Oct 15, 2026
    • Date parsed from source:
      Oct 15, 2026
    • First seen by Releasebot:
      Oct 16, 2026
    Resend logo

    Resend

    Laravel Cloud Integration

    Resend launches a Laravel Cloud integration that lets teams connect accounts with OAuth, provision environment-specific keys, and configure sending domains and sender details to send email from Laravel and PHP apps.

    Connect Resend to your Laravel Cloud applications in a few clicks.

    Sending email from a Laravel app usually means creating an API key, copying it into your environment, and configuring a sender by hand. Today, we're introducing the Laravel Cloud integration. Add Resend as a resource on your Laravel Cloud canvas, sign in with OAuth, and your environment is ready to send.

    How it works

    • Connect once: the integration is account-wide, so you authorize Resend a single time.
    • Attach anywhere: add Resend to multiple Laravel Cloud applications.
    • No keys to copy: provision keys for each environment.

    Add Resend from the canvas

    Open your application's canvas in Laravel Cloud to get started.

    Click Add resource, choose email, sign in with your Resend account, and approve access. Choose full access to manage your sending domain and sender details from within Laravel Cloud.

    Once the OAuth connection completes, pick a sending domain and set the sender name and address.

    If you haven't installed the PHP Resend package, you'll be prompted to do so within your project's dependencies. Deploy, and your app sends through Resend.

    Programmatic access

    You can also attach Resend to an environment with the Laravel Cloud API.

    curl --request POST \
    --url https://cloud.laravel.com/api/environments/{environment}/resend \
    --header 'Authorization: Bearer <token>' \
    --header 'Content-Type: application/json' \
    --data '{
      "from_address": "[email protected]",
      "from_name": "<string>",
      "key_name": "<string>",
      "reuse_key_id": "<string>"
    }'
    

    Manage access

    You can view or revoke the integration's OAuth permissions anytime from your Resend account's Team settings.

    Build with Laravel and PHP

    Once connected, use everything Resend offers from your app:

    • Send emails with Laravel using the resend/resend-laravel package.
    • Send emails with Laravel over SMTP.
    • Send emails with PHP for non-Laravel code.

    Conclusion

    Laravel Cloud and Resend now work together out of the box. Read the Laravel Cloud integration guide for full setup details.

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

    Original source
  • Oct 1, 2026
    • Date parsed from source:
      Oct 1, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Account Usage API

    Resend introduces the Usage API, giving teams and agents a direct view of account quotas and limits. Usage is also available through the CLI and MCP server, making it easier to monitor capacity and build alerts, throttling, and dashboards.

    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
  • Similar to Resend with recent updates:

  • Sep 21, 2026
    • Date parsed from source:
      Sep 21, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Duplicate Broadcast API

    Resend adds an API endpoint to duplicate any Broadcast, copying its content and settings into a draft for review before sending. The update brings more Dashboard functionality to the API, CLI, and MCP.

    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
  • Sep 16, 2026
    • Date parsed from source:
      Sep 16, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Headless Webhook API

    Resend introduces the Headless Webhook API, bringing webhook event inspection, delivery attempts, replay, and signing-secret rotation to its API, SDKs, CLI, and MCP server. Teams can automate recovery, monitor failures, and debug deliveries without relying on the dashboard.

    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
  • Sep 15, 2026
    • Date parsed from source:
      Sep 15, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    List Clicked Links API

    Resend adds an API endpoint to retrieve broadcast link clicks, including total and unique clicks ranked by popularity. Link click data is also available through the CLI and MCP server, helping teams analyze email engagement and shape future campaigns.

    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
  • Sep 14, 2026
    • Date parsed from source:
      Sep 14, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Update Segment API

    Resend adds segment renaming through the API, CLI, and MCP server, expanding segment management across its tools.

    Rename a segment from the API, CLI, or any official SDK.

    You could already create, retrieve, list, and delete segments from the API. Today we're adding PATCH /segments/:id so you can rename a segment the same way.

    Renaming a segment

    Pass the segment ID and the new name.

    The response confirms the rename:

    {
      "object": "segment",
      "id": "78261eea-8f8b-4381-83c6-79fa7120f1cf"
    }
    

    Renaming segments is also available in the Resend CLI and through the MCP server.

    Original source
  • Sep 10, 2026
    • Date parsed from source:
      Sep 10, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    New Table Component

    Resend adds a Table component to Broadcast and Template editors, with customizable rows, columns, headers, alignment, and styling. Tables support text, images, and variables, and can be created by pasting Markdown for clearer, more scannable emails.

    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
  • Sep 8, 2026
    • Date parsed from source:
      Sep 8, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Vercel v0 Integration

    Resend launches a Vercel v0 integration that lets developers add email to their projects without leaving v0. It automatically configures API keys and DNS, with billing managed through v0, making setup simpler for builders.

    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
  • Sep 3, 2026
    • Date parsed from source:
      Sep 3, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Link Checker

    Resend adds a link checker to the Broadcast and Template editors, flagging broken, missing, invalid, placeholder, and anchor links so you can fix them before sending or publishing.

    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
  • Sep 1, 2026
    • Date parsed from source:
      Sep 1, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Single Sign-On

    Resend adds Single Sign-On, letting teams sign in through their identity provider and automatically adding eligible users as members. Admins can enforce IdP-only access or restrict users to their SSO organization. SSO is an add-on for Scale plans and included with Enterprise.

    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
  • Aug 31, 2026
    • Date parsed from source:
      Aug 31, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Update API Key Name

    Resend adds API, CLI, and MCP support for renaming API keys without rotating tokens or changing permissions and domain restrictions, helping teams keep key names organized across provisioning workflows and integrations.

    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
  • Aug 28, 2026
    • Date parsed from source:
      Aug 28, 2026
    • First seen by Releasebot:
      Oct 14, 2026
    Resend logo

    Resend

    Share Email API

    Resend releases an API endpoint for creating temporary, shareable links to read-only views of sent or received emails, bringing dashboard email sharing to code, the CLI, and MCP workflows.

    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
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.