Templates let you design an email once (HTML, subject, sender) and then reuse it with different merge variables every time you send. You can create them in the Mandrill dashboard UI, or via the API (Step 7). Either way, this endpoint — POST /templates/list — shows you all the templates on your account.

Try it

No templates found. ' . 'Create one.'; } else { echo '

' . count($rows) . ' templates

'; echo ''; foreach ($rows as $row) { echo ''; echo ''; echo ''; echo ''; echo ''; echo ''; echo ''; } echo '

Slug	Name	Subject	From	Updated
`' . h($row['slug'] ?? '') . '`	' . h($row['name'] ?? '') . '	' . h($row['subject'] ?? '') . '	' . h($row['from_email'] ?? '') . '	' . h($row['updated_at'] ?? '') . '

'; } } render_debug($result); } ?>

The call

$result = mandrill_call('/templates/list', [
    'label' => 'welcome-flow',  // optional filter
]);

foreach ($result['decoded'] as $tpl) {
    echo $tpl['slug'] . ' — ' . $tpl['name'];
}

Response shape

[
    {
        "slug":       "welcome-email",
        "name":       "Welcome Email",
        "labels":     ["welcome-flow"],
        "code":       "<h1>Welcome, *|FIRSTNAME|*</h1>...",
        "subject":    "Welcome to our service",
        "from_email": "noreply@yourdomain.com",
        "from_name":  "Your Company",
        "text":       "Welcome, *|FIRSTNAME|*...",
        "publish_name":       "welcome-email",
        "publish_code":       "<h1>Welcome, *|FIRSTNAME|*</h1>...",
        "publish_subject":    "Welcome to our service",
        "publish_from_email": "noreply@yourdomain.com",
        "publish_from_name":  "Your Company",
        "publish_text":       "Welcome, *|FIRSTNAME|*...",
        "published_at":       "2024-10-15 09:22:14",
        "created_at":         "2024-10-10 11:03:00",
        "updated_at":         "2024-10-15 09:22:14"
    },
    ...
]

Draft vs. published — what the two copies mean

Notice each template has two versions of every field — one plain (code, subject…) and one prefixed publish_. That's because templates have a draft / published split:

The plain fields are the draft — whatever you last saved.
The publish_* fields are the currently live version that sends will actually use.

You edit the draft freely, and then call /templates/publish to promote it to live. This prevents an in-progress edit from accidentally going out on the next send.

The key identifier when you want to send with a template is slug — a URL-safe version of the name. That's what /messages/send-template (next page) wants.

→ Next: create a template and send with it