# Email Templates API



> The email templates resource supports migrations, governance, and external template sync. This guide explains when to use templates, how to preserve structured editor content, and how to keep template names and descriptions useful for workspace users.



- Human page: https://mailrith.com/developers/email-templates

- Markdown page: https://mailrith.com/developers/email-templates.md

- Category: API Resources

- Reading time: 6 min read

- Last updated: 2026-06-13

- Related keywords: Email Templates API, Email Templates API developer docs, API Resources, API Resources developer docs, Mailrith developer docs, Mailrith public API, Manage Reusable Email Templates, Endpoint Overview, Broadcasts API, Sequences API, API Reference



## AI Agent Notes

- Use this page as implementation guidance, then validate exact endpoint fields against the OpenAPI document.

- Keep API keys server-side and workspace-scoped unless a guide explicitly says otherwise.

- Do not invent privacy, consent, or lawful-basis evidence. Send only fields that appear in the OpenAPI schema for the endpoint you are using.



## What this guide covers

Manage reusable email templates, structured editor content, and approved layout libraries.



## Manage Reusable Email Templates

Email templates are reusable layouts and content blocks that help teams create consistent emails. Teams can use templates as starting points for broadcasts, sequences, and other email workflows.

Use the email templates API for migrations from another email platform, external content governance, approved template libraries, or internal tools that keep brand-approved layouts synchronized.

Template changes can affect how users create future emails. Make template names, descriptions, and content clear enough that workspace users know when to use each template.

1. List current templates before you import a new template library.
2. Create or update one template at a time so review is easier.
3. Use a plain name and description that match how users choose templates in [Email Templates](https://mailrith.com/docs/email-templates.md).
4. Preserve structured `body_document` content exactly as the public schema expects.
5. Preview or test the template in Mailrith before you tell users to create broadcasts or sequences from the template.
6. Delete templates only after you confirm they are no longer useful as starting points.

- List templates to build a template picker in an external tool.
- Create templates when you import approved layouts or set up a new workspace.
- Update templates when your design system or approved copy changes.
- Delete templates only after you confirm they are no longer needed as starting points.

## Endpoint Overview

`GET /v1/email-templates` lists reusable templates. Item endpoints let your integration inspect, update, or delete a single template.

`POST /v1/email-templates` creates a template. The template payload includes the structured email body document that the Mailrith editor uses.

Treat `body_document` as structured editor content, not plain text. Keep the structure generated by your source system or by Mailrith's documented schema.

Related OpenAPI operation groups:
- Email Templates

**Create an Email Template**

```bash
curl -X POST https://api.mailrith.com/v1/email-templates \
  -H "Authorization: Bearer mrk_example_secret_key" \
  -H "Idempotency-Key: template-welcome-v1" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Welcome newsletter",
    "description": "Default newsletter layout for the workspace",
    "enabled": true,
    "body_document": {
      "type": "doc",
      "content": []
    }
  }'
```



## Related Guides

- [Broadcasts API](https://mailrith.com/developers/broadcasts.md): The broadcasts resource is the public campaign control plane for one-off messages. This guide explains draft management, test sends, live-send safety, and why integrations and agents should treat send actions as high-impact operations.

- [Sequences API](https://mailrith.com/developers/sequences.md): The sequences resource lets external systems prepare, migrate, or synchronize time-based email series. This guide explains how to plan sequence definitions, when to update or delete sequences, and what to check before migrated journeys reach real subscribers.

- [API Reference](https://mailrith.com/developers/api-reference.md): The full API reference is generated from the same public contract used by the API worker and SDK tooling. Use the API reference to find exact paths, methods, parameters, request schemas, response schemas, operation IDs, and the downloadable OpenAPI document.