send-email

Send transactional and bulk emails via the Resend API.

63|2|Updated Mar 23, 2026

Search Tags:#webhooks #idempotency #deliverability #batch-processing #send-email #transactional-emails #resend-api

Ready to run

npx skills add https://github.com/stolinski/s-stack --skill send-email-stolinski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: send-email
Source: https://github.com/stolinski/s-stack/tree/main/skills/resend/send-email
Command: npx skills add https://github.com/stolinski/s-stack --skill send-email-stolinski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sending transactional and bulk emails via the Resend API simplifies development workflows by removing manual SMTP setup and providing reliable delivery with built-in safeguards.

Core Features & Use Cases

Single emails via POST /emails for individual messages (with attachments and scheduling support)
Batch emails via POST /emails/batch for multiple messages in one request
Idempotency keys, error handling, and retry strategies to ensure production reliability
Webhooks and deliverability guidance to monitor delivery status and maintain compliance

Quick Start

Detect your project language, install the appropriate Resend SDK, and implement a single or batch email flow with idempotency keys.

Frequently Asked Questions about send-email

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I send transactional emails using the Resend API?▼

To send transactional emails with the Resend API, you make requests to the POST /emails endpoint for single messages or POST /emails/batch for bulk notifications. This replaces manual SMTP setup by handling welcome messages, order confirmations, and password resets programmatically via SDKs or cURL.

What is the best way to handle bulk email delivery and ensure reliability?▼

The best way to handle bulk email delivery is using the POST /emails/batch endpoint combined with idempotency keys. Idempotency keys prevent duplicate email sends during network retries, while robust error handling and retry strategies ensure production reliability for your batch processing workflows.

Do I need a specific API key to send emails through Resend?▼

Yes, you need a Resend API key to authenticate requests to the /emails and /emails/batch endpoints. This key is required to programmatically send transactional and bulk emails, manage attachments, and utilize optional scheduling features within your application.

How do webhooks work with transactional email delivery?▼

Webhooks integrate with your transactional email delivery to monitor delivery status and maintain compliance. By configuring webhook integrations alongside your Resend API sends, you receive automated updates on whether your emails were successfully delivered or encountered issues.

Can I schedule emails and add attachments when sending via Resend?▼

Yes, you can schedule emails and add attachments when sending messages via the Resend API. The POST /emails endpoint supports optional scheduling and attachments, allowing you to send individual transactional messages with files at specified times using SDKs or cURL.

Why use idempotency keys for batch processing transactional emails?▼

You use idempotency keys for batch processing transactional emails to prevent duplicate sends during network failures or retry attempts. By including these keys in your POST /emails/batch requests, you ensure production reliability and avoid sending multiple identical notifications to users.