# Create a template version

Adds a new template version. If the template doesn’t contain any other versions, the first version becomes active. A template can store up to 40 versions.

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

## Path parameters:

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

  - `template_name` (string, required)
    template name to create the new version for.

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

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

  - `tag` (string, required)
    Tag of the version that is being created. Must be unique to the template.

  - `comment` (string)
    Comment related to the version that is being created.

  - `active` (string)
    If this flag is set to yes, this version becomes active

  - `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