Create a message template

Array of media attachments to include when sending messages with this template.

Alternatively, you can use the media_urls parameter with an array of URL strings.

Alternative message bodies to use instead of the default message body when their conditions match, when sending messages with this template. Allows sending different message bodies depending on the route that sends the message, or the contact that the message is sent to. Each variant has conditions and its own message body. When each message is sent, the first variant whose conditions match is used instead of the default message body; if no variant matches, the default message body is used. A variant replaces the entire message body: content, media, route_params, track_clicks and short_link_params that are not specified in the variant are empty, not inherited from the default message body. Conditions are evaluated when the message is sent by a particular basic route, and can use the same variables as outgoing message content: contact variables such as [[contact.name]] and [[contact.vars.*]], [[to_number]], [[time]], [[project.*]], and variables of the basic route sending the message: [[phone.type]] (e.g. whatsapp), [[phone.id]], [[phone.vars.*]], and [[phone.supports_quick_replies]], [[phone.supports_link_button]], [[phone.supports_native_attachments]] (1 if the route supports the feature, otherwise 0). Variables may include filters, e.g. [[contact.vars.language|default:"en"]]. For all available variables, see the Variable Reference.

For A/B testing, a variant can have a random split (split_percent) so that it is only used for a random percentage of recipients, e.g. a single variant with split_percent 50 is used for about half of the recipients, and the default message body for the others. A random split can be combined with other conditions to run separate A/B tests for different routes or contacts.

Since the first matching variant is used, list more specific variants before more general ones. For example, a variant with a condition [[contact.vars.language]] is 'fr' and split_percent 50 must be listed before a variant with only the condition [[contact.vars.language]] is 'fr'. Up to 10 variants are supported, each with up to 5 conditions.

Array of media attachments to include when sending messages with this template. When updating this field, each item is an object with a url or file_id property (and optionally type and filename), in the same format as the media parameter of project.sendMessage.

Alternative message bodies to use instead of the default message body when their conditions match, when sending messages with this template. Allows sending different message bodies depending on the route that sends the message, or the contact that the message is sent to. Each variant has conditions and its own message body. When each message is sent, the first variant whose conditions match is used instead of the default message body; if no variant matches, the default message body is used. A variant replaces the entire message body: content, media, route_params, track_clicks and short_link_params that are not specified in the variant are empty, not inherited from the default message body. Conditions are evaluated when the message is sent by a particular basic route, and can use the same variables as outgoing message content: contact variables such as [[contact.name]] and [[contact.vars.*]], [[to_number]], [[time]], [[project.*]], and variables of the basic route sending the message: [[phone.type]] (e.g. whatsapp), [[phone.id]], [[phone.vars.*]], and [[phone.supports_quick_replies]], [[phone.supports_link_button]], [[phone.supports_native_attachments]] (1 if the route supports the feature, otherwise 0). Variables may include filters, e.g. [[contact.vars.language|default:"en"]]. For all available variables, see the Variable Reference.

For A/B testing, a variant can have a random split (split_percent) so that it is only used for a random percentage of recipients, e.g. a single variant with split_percent 50 is used for about half of the recipients, and the default message body for the others. A random split can be combined with other conditions to run separate A/B tests for different routes or contacts.

Since the first matching variant is used, list more specific variants before more general ones. For example, a variant with a condition [[contact.vars.language]] is 'fr' and split_percent 50 must be listed before a variant with only the condition [[contact.vars.language]] is 'fr'. Up to 10 variants are supported, each with up to 5 conditions.