Skip to content

Create email template

post

/templates/email/create

Use this endpoint to create email templates on the Braze dashboard.

These templates will be available on the Templates & Media page. The response from this endpoint includes a field for email_template_id, which can be used to update the template in subsequent API calls.

Prerequisites

To use this endpoint, you’ll need an API key with the templates.email.create permission.

Rate limit

We apply the default Braze rate limit of 250,000 requests per hour to this endpoint, as documented in API rate limits.

Request body

Request parameters

Parameter Required Data Type Description
template_name Required String Name of your email template.
subject Required String Email template subject line.
body Required String Email template body that may include HTML.
plaintext_body Optional String A plaintext version of the email template body.
preheader Optional String Email preheader used to generate previews in some clients.
tags Optional String Tags must already exist.
should_inline_css Optional Boolean Enables or disables the inline_css feature per template. If not provided, Braze will use the default setting for the app group. One of true or false is expected.

Example request

Example response

Troubleshooting

The following table lists possible returned errors and their associated troubleshooting steps, if applicable.

Error Troubleshooting
Template name is required Enter a template name.
Tags must be an array Tags must be formatted as an array of strings, for example ["marketing", "promotional", "transactional"].
All tags must be strings Make sure your tags are encapsulated in quotes ("").
Some tags could not be found To add a tag when creating an email template, the tag must already exist in Braze.
Email must have valid Content Block names The email might contain Content Blocks that don’t exist in this environment.
Invalid value for should_inline_css. One of true or false was expected This parameter only accepts boolean values (true or false). Make sure the value for should_inline_css is not encapsulated in quotes (""), which causes the value to be sent as a string instead.
HOW HELPFUL WAS THIS PAGE?
New Stuff!