Resend

Join us for Forward, an event for builders. - October 21, 2026 - San Francisco, California - Early-bird pricing

Need more help working with our test email addresses? resend.com/docs/dashboard…

You can even use + labels to track different tests or users, which is handy for keeping test scenarios separate in webhooks and logs. 🔸 delivered+user1@resend.dev 🔸 bounced+user1@resend.dev 🔸 complained+user1@resend.dev

🔥 Pro Tip: Testing 🔥 Any address in a test send is a real recipient. The API tries to deliver, and addresses on reserved TLDs (.local, .test, .invalid, etc.) come back as bounces because they don't resolve, which counts against your reputation. A real scenario 👇

@truthixifi On the Billing page page, you can click on the "..." to revert the cancellation decision.

@resend I canceled my subscription for pro and it will cancel on July 20th, I later figured I’ll need the service and want to revert the decision but I can’t find a way to do that, do I have to wait till July 20th to renew it?

Read the full changelog for more 👇 resend.com/changelog/oaut…

OAuth turns Resend into something users can safely plug into any app, and it's the same foundation behind our remote MCP server. For the full walkthrough, including both remote and local options, see our docs. resend.com/docs/guides/bu…

4️⃣ Call the API with the access token You get back a JWT access token and an opaque refresh token. Pass the access token as a Bearer token to any route your scope allows.

3️⃣ Exchange the code for tokens Send the original code_verifier using the preferred form encoding.

2️⃣ Generate PKCE values and send the user to authorize Every authorization code exchange requires PKCE, so generate a code_verifier, its code_challenge, and a state value before you redirect. Open the authorization URL in the user's browser so they see the consent screen.

1️⃣ Register your client Call the Register Client endpoint to dynamically register your OAuth client. The response returns a UUID client_id.

What you can build with it 🔸 Desktop and CLI tools 🔸 Hosted integrations 🔸 Agents and MCP hosts Here's how it works 👇

Users can review and revoke any app's access from their Resend account's Team settings.

Today, we're adding OAuth to the Resend API. Authorization URL → user approves → scoped access token. Resend implements OAuth 2.1, plus Dynamic Client Registration for clients like MCP hosts that can't know their deployment details ahead of time.

As @meowgorithm, Charm's Co-Founder & CEO puts it, the OAuth layer is much better DX with improved to security!

We're proud to launch with OAuth powering @charmcli's Pop. github.com/charmbracelet/…

@JoMorency 🫶

Resend is such a huge part of our automated system at @HaitiBrand

Prefer YouTube? youtu.be/IYg6CAR9wSE

Using the Connector, you can: 🔸 send/receive emails 🔸 test webhook events 🔸 create events and automations 🔸 generate templates And so much more. More than 85 precision tools. View everything you can do 👇 resend.com/docs/mcp-server

Resend is now available as a @claudeai Connector. Add to Claude Desktop or Claude Web to: • send emails • debug email logs • create Automations • build Broadcasts from Figma 2 minute quickstart👇