Everything smashsend.com publishes
S

smashsend.com

SMASHSEND Emails API Reference

/docs/api/emails

docs
Words
1,507
Reading time
7 min
Last crawled
2026-09-27
Language
EN
A1

Opening

Home / Docs / API Reference / Emails The SMASHSEND Emails API allows you to send transactional emails using three powerful methods: raw HTML emails for complete control, templated emails for consistency, and React compon

A2

Overview

All email endpoints require authentication via API keys with scope. You can send individual emails or batch multiple emails in a single request. Base URL: Rate Limits: Batch requests support up to 50 emails per request.

A3

Authentication

All requests must include your API key in the Authorization header:

A4

Verified From Addresses

Important: You can only send emails from verified email addresses or domains. If you attempt to send from an unverified address, you'll receive a 400 error with a list of allowed emails and domains. To add custom domains

A5

Send Single Email

Send a single transactional email using either raw HTML content, a predefined template, or a React component. This endpoint supports both immediate sending and scheduled delivery.

A6

Method 1: Raw HTML Email

Send emails with complete control over HTML content, styling, and structure. Perfect for custom designs and one-off emails. Request Body (Raw Email) Request Example

A7

Method 2: Templated Email

Use predefined email templates created in your SMASHSEND dashboard. Templates support variable substitution for personalization. Request Body (Templated Email) Request Example

A8

Method 3: React Component Email

Generate emails using React components for dynamic, maintainable email templates. This approach renders React components to HTML and sends them as raw emails. JavaScript Example with React Email Response (All Methods) PO

B1

Send Batch Emails

Send up to 50 emails in a single request. You can mix raw and templated emails in the same batch request. Request Body Request Example Response

B2

Request Parameters

Raw Email Parameters (required) - Sender email address or "Name " format (optional) - Sender display name (required) - Recipient email address (required) - Email subject line (required) - HTML email content (optional) -

B3

Error Handling

The API returns standard HTTP status codes. Common error responses: 400 Bad Request - Invalid From Email 400 Bad Request - Invalid Payload 401 Unauthorized 403 Forbidden - Sending Limits

B4

Best Practices

Choosing the Right Method • Raw HTML: Use for one-off emails, highly customized designs, or when you need complete control over the HTML structure • Templates: Best for recurring email types like welcome emails, notifica

B5

Common Use Cases

User Onboarding Flow Order Confirmation with Dynamic Content Batch Newsletter Sending