The `HTML` content type allows you to send raw HTML emails with full design control. Use this when you have existing HTML templates or need pixel-perfect layouts. Building templates as React components? See [Send React Email Templates with Lumail](/docs/tutorials/react-email). ## Quick Example ```bash curl -X POST https://lumail.io/api/v1/emails \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "to": "user@example.com", "subject": "Welcome {{name}}!", "content": "

Hello {{name}}!

Welcome to our platform.

", "contentType": "HTML", "from": "hello@yourdomain.com" }' ``` ```typescript import { Lumail } from "lumail"; const lumail = new Lumail({ apiKey: "YOUR_API_TOKEN" }); await lumail.emails.send({ to: "user@example.com", subject: "Welcome {{name}}!", content: "

Hello {{name}}!

Welcome to our platform.

", contentType: "HTML", from: "hello@yourdomain.com", }); ``` ## Variable Substitution Use double curly braces in your HTML to insert subscriber data: ```html

Hello {{name | 'Friend'}}!

Your email is {{email}}.

``` ### Available Variables | Variable | Description | | -------------------- | ----------------------------------------------- | | `{{name}}` | Subscriber's name | | `{{email}}` | Subscriber's email address | | `{{phone}}` | Subscriber's phone number | | `{{unsubscribeUrl}}` | Unsubscribe link (empty on transactional sends) | | `{{onlineUrl}}` | View in browser link | | `{{customField}}` | Any custom field | Placeholder names must be word characters. Hyphenated organization variables such as `{{org-name}}` are not substituted in `HTML` content and are delivered literally. ## Complete Example ```json { "to": "customer@example.com", "subject": "Your order #{{orderNumber}} is confirmed!", "contentType": "HTML", "content": "

Thanks for your order, {{name}}!

Your order #{{orderNumber}} has been confirmed.

Total:	{{orderTotal}}
Shipping:	{{shippingMethod}}

Questions? Contact us

", "from": "orders@yourstore.com", "preview": "Your order has been confirmed" } ``` ## Email-Safe HTML Guidelines ### Use Inline Styles Email clients have limited CSS support. Always use inline styles: ```html

Hello!

``` ### Use Tables for Layout For complex layouts, use tables instead of flexbox or grid: ```html

Left column

Right column

``` ### Set Image Dimensions Always specify width and height for images: ```html

``` ### Use Web-Safe Fonts Stick to fonts available on all systems: ```html

Safe fonts

Safe serif

``` ## Automatic Features When using HTML format, Lumail automatically: - **Adds unsubscribe link** on non-transactional sends when `{{unsubscribeUrl}}` is absent (appended at the bottom) - **Adds tracking pixel** for open tracking, inserted before `` - **Generates plain text** version by stripping HTML tags Click tracking rewrites Markdown-style `[text](url)` links, so `` URLs in HTML content are delivered unchanged. ## Including Unsubscribe Link If you want to control the placement of the unsubscribe link, include it in your HTML: ```html

Unsubscribe

``` If you don't include `{{unsubscribeUrl}}`, Lumail will automatically append an unsubscribe link at the bottom of your email. ## Best Practices 1. **Test across email clients** - Use tools like Litmus or Email on Acid 2. **Keep width under 600px** - Ensures proper display on mobile 3. **Use alt text for images** - Many clients block images by default 4. **Avoid JavaScript** - Not supported in email clients 5. **Include plain text fallback** - Lumail generates this automatically 6. **Use absolute URLs** - Relative URLs won't work in emails ## API Reference **Method:** POST **Endpoint:** /api/v1/emails