Your account at {{company}} has been created successfully.
``` **In the request body (public v1 API):** ```json theme={null} { "template_id": "550e8400-e29b-41d4-a716-446655440000", "variables": { "name": "Carlos", "company": "TechStore" } } ``` **Rendered result:** ```html theme={null}Your account at TechStore has been created successfully.
``` In `/v1/send-template-email` (the `variables` field), additionally: * `{variableName}` with a single brace is equivalent to `{{variableName}}`. * You can define a fallback with `{variable || "default value"}` for when the variable doesn't exist. * Values are HTML-escaped by default; use `{!variable}` to insert unescaped HTML. * Variables with no value (and no fallback) render as an empty string. In the advanced API (`/send-email`, the `data` field), always use double braces `{{variable}}`. Single braces and `||` fallbacks are not available, and values are inserted without HTML escaping. *** ### Conditionals > Available only in the **advanced API** (`POST /send-email`, the `data` field). `/v1/send-template-email` does not support `{{#if}}` blocks. Use `{{#if variable}}...{{/if}}` to show content only when a variable exists and is truthy. Use `{{else}}` for the opposite case. **In the template:** ```html theme={null} {{#if premium}}Thanks for being a Premium member. You get free shipping on all your orders.
{{else}}Upgrade to Premium to get free shipping.
{{/if}} ``` **In the request body:** ```json theme={null} { "data": { "premium": true } } ``` > **Note:** Handlebars evaluates the values `false`, `undefined`, `null`, `""`, `0`, and empty arrays `[]` as falsy. *** ### Loops Use `{{#each array}}...{{/each}}` to iterate over a list. Available in both APIs, with different syntax inside the block. **In the advanced API** (`/send-email`, the `data` field), `{{this}}` is the current item. Access its properties with `{{this.property}}` and use helpers: ```html theme={null}| Product | Quantity | Price |
|---|---|---|
| {{this.name}} | {{this.quantity}} | {{formatCurrency this.price}} |
Total: {{formatCurrency total}}
``` With `"total": 61970` it produces: `$61,970.00` To use another currency: ```html theme={null}Total: {{formatCurrency total "CLP"}}
``` ### `multiply` Multiplies two numeric values. The result is rounded to 2 decimals. ```html theme={null}Subtotal: {{formatCurrency (multiply quantity price)}}
``` ### `formatDate` Formats an ISO 8601 date into a human-readable Spanish format (`es-ES`). Accepts an optional second parameter for the format. **Default format (`short`):** ```html theme={null}Date: {{formatDate deliveryDate}}
``` With `"deliveryDate": "2025-03-15T00:00:00Z"` it produces: `15/3/2025` **Long format (`long`):** ```html theme={null}Date: {{formatDate deliveryDate "long"}}
``` With `"deliveryDate": "2025-03-15T00:00:00Z"` it produces: `sábado, 15 de marzo de 2025` ### `default` Provides a default value when the variable is falsy (`undefined`, `null`, `""`, `0`, or `false`). ```html theme={null}Hello, {{default name "Customer"}}!
``` If `name` is not defined in `data`, it renders as `Hello, Customer!`. ### `json` Serializes an object to JSON with indentation. Useful for debugging or including structured data in the email. ```html theme={null}{{json data}}
```
With `"data": {"key": "value"}` it produces:
```json theme={null}
{
"key": "value"
}
```
The text helpers `capitalize`, `uppercase`, and `lowercase` are also available to transform strings.
***
## Identifying a template
You can reference a template in two ways in the public API (`/v1/send-template-email`):
| Field | Type | Description |
| ---------------------- | ------------- | ------------------------------------------ |
| `template_id` | string (UUID) | Unique UUID of the template |
| `template_internal_id` | number | Auto-incremented internal ID (per project) |
```json theme={null}
{
"template_id": "550e8400-e29b-41d4-a716-446655440000",
"recipient_email": "user@example.com",
"sender_email": "store@yourdomain.com",
"variables": {
"name": "Ana",
"orderNumber": "5021"
}
}
```
* If the template doesn't exist, the API returns a `404` error.
* `template_internal_id` is resolved within the project associated with the API key used.
In the advanced API (`/send-email`), the `templateId` field accepts the template's UUID or its numeric internal ID, always within the project associated with the API key.
***
## The `variables` object
In `/v1/send-template-email`, the `variables` object is a JSON where each key is a template variable. Values are converted to strings when rendering. Variables the template uses but that don't exist render as an empty string (or with their `||` fallback if defined).
### Complete example
**Request:**
```bash theme={null}
curl -X POST https://api.reallyquickemails.com/v1/send-template-email \
-H "Authorization: Bearer sk_proj_xxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{
"template_id": "550e8400-e29b-41d4-a716-446655440000",
"recipient_email": "john.doe@example.com",
"sender_email": "orders@mystore.com",
"variables": {
"name": "John",
"orderNumber": "3847",
"purchaseDate": "February 20, 2026",
"products": [
{ "product": "Bluetooth Headphones", "quantity": 1, "price": "$34.990" },
{ "product": "USB-C Cable", "quantity": 3, "price": "$5.990" }
],
"total": "$52.960"
}
}'
```
**Corresponding template (v1 syntax):**
```html theme={null}
Order #{{orderNumber}} - {{purchaseDate}}
| {{product}} | x{{quantity}} | {{price}} |
Total: {{total}}
Handled by: {salesRep || "our team"}
``` This engine does not include formatting helpers: send prices and dates already formatted as strings. For conditionals, helpers, or nested properties, use the advanced API (`POST /send-email`) with `templateId` + `data`. *** ## Accessing nested properties In the advanced API (`/send-email`, the `data` field), use dot notation to access nested objects: ```html theme={null}City: {{address.city}}
Region: {{address.region}}
``` ```json theme={null} { "data": { "address": { "city": "Santiago", "region": "Metropolitana" } } } ``` In `/v1/send-template-email`, dot notation is **not** supported: flatten the variables before sending them (for example `address_city` instead of `address.city`). *** ## Best practices * **Define default values for optional variables:** in the advanced API use the `default` helper; in v1 use `{variable || "value"}` fallbacks. This avoids blank spaces in the email. * **Validate your variables before sending.** Variables the template expects but that don't exist render as empty strings, without error. * **Store the `template_id` (UUID) in your configuration**, or use `template_internal_id` if you prefer short numeric IDs per project. * **Test your templates** with sample data before integrating. In the advanced API use `dry_run: true` to render without sending — see [Dry Run](/en/api-reference/send-email#dry-run).