send-email

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.

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.

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.

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.

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.

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.