Templates API
The Templates API provides full CRUD (Create, Read, Update, Delete) operations for managing reusable email templates. You can create, list, view, update, and delete templates programmatically to use across broadcasts, sequences, and transactional emails.
Required Permissions
All endpoints require authentication via an API token with appropriate permissions:
- Read Permission: Required for GET endpoints (list, show)
- Write Permission: Required for POST, PATCH, DELETE endpoints
Template Object
The template object contains the following fields:
| Field | Type | Description |
|---|---|---|
| `id` | integer | The unique identifier of the template |
| `label` | string | The internal name of the template (must be unique per channel) |
| `subject` | string | The subject line of the email |
| `preheader` | string | Preview text that appears in email clients |
| `body` | string | The content of the email (plain text or HTML) |
| `html_body` | boolean | Whether the body contains HTML content (default: false) |
| `created_at` | datetime | When the template was created |
| `updated_at` | datetime | When the template was last updated |
List Templates
GET /api/v1/templates
Retrieve a list of all templates for the authenticated broadcast channel, ordered alphabetically by label.
Query Parameters
limit(optional): Maximum number of templates to returnoffset(optional): Number of templates to skip for pagination
Request
curl -X GET \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ http://your-domain.com/api/v1/templates
Response
{ "data": [ { "id": 1, "label": "Monthly Newsletter", "subject": "Your Monthly Update", "preheader": "See what's new this month", "body": "<p>Newsletter content here</p>", "html_body": true, "created_at": "2024-01-01T12:00:00Z", "updated_at": "2024-01-01T12:00:00Z" }, { "id": 2, "label": "Welcome Email", "subject": "Welcome to Our Community!", "preheader": "Thanks for joining us", "body": "<p>Welcome content here</p>", "html_body": true, "created_at": "2024-01-02T10:00:00Z", "updated_at": "2024-01-02T10:00:00Z" } ], "total": 2 }
Get Template
GET /api/v1/templates/:id
Retrieve details of a specific template.
Request
curl -X GET \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ http://your-domain.com/api/v1/templates/123
Response
{ "id": 123, "label": "Welcome Email", "subject": "Welcome to Our Community!", "preheader": "Thanks for joining us", "body": "<p>Welcome to the community! We're excited to have you.</p>", "html_body": true, "created_at": "2024-01-01T12:00:00Z", "updated_at": "2024-01-01T12:00:00Z" }
Create Template
POST /api/v1/templates
Create a new email template.
Parameters
label(required): Internal name of the template (must be unique per channel)subject(required): Subject line of the emailbody(required): Content of the emailpreheader(optional): Preview text that appears in email clientshtml_body(optional): Whether the body contains HTML (default: false)
Request
curl -X POST \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "template": { "label": "Welcome Email", "subject": "Welcome to Our Community!", "preheader": "Thanks for joining us", "body": "<p>Welcome to the community! We are excited to have you.</p>", "html_body": true } }' \ http://your-domain.com/api/v1/templates
Response
{ "id": 123 }
Notes
- The
labelmust be unique within your broadcast channel - If
html_bodyis set totrue, the body should contain valid HTML - Line breaks in HTML should use
<br>tags, and paragraphs should be wrapped in<p>tags
Update Template
PATCH /api/v1/templates/:id
Update an existing template.
Parameters
All parameters are optional. Only include the fields you want to update:
label: Internal name of the templatesubject: Subject line of the emailbody: Content of the emailpreheader: Preview text that appears in email clientshtml_body: Whether the body contains HTML
Request
curl -X PATCH \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "template": { "subject": "Updated Subject Line", "body": "<p>Updated content</p>" } }' \ http://your-domain.com/api/v1/templates/123
Response
{ "id": 123, "label": "Welcome Email", "subject": "Updated Subject Line", "preheader": "Thanks for joining us", "body": "<p>Updated content</p>", "html_body": true, "created_at": "2024-01-01T12:00:00Z", "updated_at": "2024-01-01T12:30:00Z" }
Delete Template
DELETE /api/v1/templates/:id
Delete a template.
Request
curl -X DELETE \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ http://your-domain.com/api/v1/templates/123
Response
{ "message": "Template deleted successfully" }
Error Responses
If the request is invalid, the response will include an appropriate HTTP status code and error message:
401 Unauthorized
{ "error": "Unauthorized" }
This error occurs when: - No authorization header is provided - The token is invalid or expired - The token doesn’t have the required permissions
404 Not Found
{ "error": "Template not found" }
This error occurs when: - The template ID doesn’t exist - The template belongs to a different broadcast channel
422 Unprocessable Entity
{ "error": "Label can't be blank, Subject can't be blank, Body can't be blank" }
This error occurs when: - Required fields are missing - The label is already taken by another template in the same channel - Validation fails for any other reason
Usage Example: Syncing Templates from External System
Here’s an example of how you might sync templates from an external system:
# First, list existing templates curl -X GET \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ http://your-domain.com/api/v1/templates # Create a new template if it doesn't exist curl -X POST \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "template": { "label": "Product Update", "subject": "New Product Features", "preheader": "Check out what is new", "body": "<h1>New Features</h1><p>We have exciting updates to share!</p>", "html_body": true } }' \ http://your-domain.com/api/v1/templates # Update an existing template curl -X PATCH \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "template": { "body": "<h1>New Features</h1><p>Updated content with more details!</p>" } }' \ http://your-domain.com/api/v1/templates/123