resend_skill

Overview

This skill provides curl-based recipes for using the Resend REST API to send transactional emails, manage contacts, verify domains, and administer API keys. It focuses on practical, copy-paste shell examples and minimal setup steps to get started quickly. Use it to automate email delivery and contact management from scripts or CI jobs.

How this skill works

The skill issues authenticated HTTP requests to Resend endpoints using curl. It reads JSON payloads from temporary files and sets the RESEND_API_KEY environment variable for authorization. Common operations covered include single and batch sends, scheduling, retrieving status, contact CRUD, domain verification, and API key management.

When to use it

• Send transactional emails like welcome messages, password resets, or notifications from scripts.
• Dispatch batch emails (up to 100 per request) for targeted campaigns or multi-recipient notifications.
• Manage contact records and custom properties from automation or backend jobs.
• Verify and manage sending domains before moving to production sending.
• Create, list, or revoke API keys for automation and access control.

Best practices

• Set RESEND_API_KEY as an environment variable and use bash -c '...' when piping to curl to avoid variable clearing.
• Verify sender domains in production; use the onboarding test address only for development.
• Respect the 2 requests/sec rate limit and implement exponential backoff on 429 responses.
• Use Idempotency-Key header for operations that must not be duplicated (e.g., send retries).
• Batch up to 100 emails with /emails/batch to reduce request count and improve throughput.

Example use cases

• Trigger a password reset email from a backend job by writing a JSON payload and POSTing to /emails.
• Schedule a follow-up email in 1 hour using the scheduledAt natural language field.
• Import or update contact records with custom properties for segmentation.
• Provision a new sending domain and call the verify endpoint via automation.
• Rotate API keys by creating a new key with permissions and deleting the old key via script.