Resend

What part of a password reset does Resend handle?

Resend sends the email with your reset link. Your app or sign-in service decides when to send it, creates the link and checks that it can only be used as intended.

A receipt works the same way. Your app confirms the purchase and hands Resend the address and message. If your sign-in service connects through SMTP, the standard way for apps to hand off outgoing mail, you can use that connection instead of calling the email service from your app code.

How do I test without emailing customers?

Use Resend’s special test recipients to simulate delivery, a bounce or a spam complaint.

• Try a simulated delivery and bounce, then find each result in the email history. These tests count against your sending quota.
• To try the default sender with a real inbox, use the email on your Resend account for a disposable user in your app. Request one reset and check that the link works.
• Before sending to customers, verify a domain you control. Add the records Resend gives you where you manage the domain, wait for verification, and switch to a From address on that domain. Keep the sending key in the server or sign-in service.

Where do I look if a reset email never arrives?

Find the message in Resend using the reference your app saved when it tried to send. Check whether it was accepted for sending, accepted by the receiving mail server, delayed, bounced or skipped.

A receiving mail server can accept the message and still put it in junk or quarantine. If Resend reports a permanent bounce or spam complaint, check the address and reason before trying again. Resend automatically stops sending to such addresses across the team’s sending domains. Its suppression list shows which addresses are paused and why.

If your app receives automatic delivery updates, verify that each update came from Resend before it changes a customer’s record. Keep provider details in your support tools.

• See the suppression list in ResendResend’s screenshot shows the blocked address and the reason it was added.

How do I avoid sending the same receipt twice?

Give the receipt a stable identifier based on the purchase. If you control the send request and it times out, reuse the same Resend duplicate-protection key for the same request. Resend remembers those keys for 24 hours.

Record the send operation once in your app before attempting delivery. Save any message reference you receive. If the result remains uncertain after the protection window, check the send history before attempting another send.

How many messages fit in the free plan?

The transactional Free plan includes 3,000 emails per month and 100 per UTC calendar day. Each recipient counts separately, and received messages and simulated test emails also use the quota.

A receipt sent to one customer with one copied address uses two email units. A day with 120 recipients exceeds the daily free allowance even if you send very little the rest of the month.

The listed Pro example is $20 USD per month for 50,000 emails with no daily email quota. If you enable paid overages, this tier lists $0.90 USD for each extra block of 1,000 emails. Sending stops at the monthly quota if overages are off. If they are on, sending pauses when you reach your team’s overage cap. Check that cap in Usage before a busy month. Marketing broadcasts use a separate contacts-based plan.

What can I keep when I change email services?

On active Free, Pro and Scale accounts, Resend’s standard email and log history is 30 days. Enterprise has separate retention options. Export the records you need while they are available.

Team admins have seven days to download a generated export. Resend lists CSV exports for sent and received email records and logs. Check the fields you need and keep your receipt and reset templates separately. You can list suppression entries through the API.

Resend says it stores customer data, including saved email content and logs, in the US regardless of the sending region you choose.

Keep a record of send operations in your app. Configure the new sender and credentials, then test one send and one failed-delivery event before moving customer mail.