# Create a template

Store a new template, including its name, description and (optionally) the template content. If the template content is provided, a new version is automatically created and becomes the active version.

Endpoint: POST /v3/{domain_name}/templates
Version: 3.0.0
Security: basicAuth

## Path parameters:

  - `domain_name` (string, required)
    Domain name the template is associated with.

## Request fields (multipart/form-data):

  - `name` (string, required)
    Name of the template being stored. Supports utf-8 characters and name will be down cased.

  - `description` (string)
    Description of the template being stored

  - `createdBy` (string)
    Optional metadata field api user can indicate who created the template.

  - `template` (string)
    Content of the template.

  - `tag` (string)
    Initial tag of the created version. If the template parameter is provided and the tag is missing, the default value  is used.

  - `comment` (string)
    Version comment. This is valid only if a new version is being created. (template parameter is provided.)

  - `headers` (string)
    Key value JSON object of headers to be stored with the template. Where key is the header name and value is the header value. The header names , , and  are the only ones currently supported.  These headers will be inserted into the MIME at the time we attempt delivery. 

Headers set at the message level will override headers set on the template. e.g. Setting the From header at the time of sending will override the From header saved on the template. Additionally, headers generated by templates are not reflected on the accepted event as they are not prepended to the message until the message is prepped for delivery. if a From header is not provided either in the message or template, we will default to

## Response 200 fields (application/json):

  - `message` (string, required)
    Response message

  - `template` (any, required)
    Template details