An HTML template that can establish a consistent design for transactional emails.
Each parent account, as well as each Subuser, can create up to 300 different transactional templates. Templates are specific to the parent account or Subuser, meaning templates created on a parent account will not be accessible from the parent's Subuser accounts.
Transactional templates are templates created specifically for transactional email and are not to be confused with Marketing Campaigns designs. For more information about transactional templates, please see our Dynamic Transactional Templates documentation.
This endpoint allows you to retrieve all transactional templates.
Bearer <<YOUR_API_KEY_HERE>>The on-behalf-of header allows you to make API calls from a parent account on behalf of the parent's Subusers or customer accounts. You will use the parent account's API key when using this header. When making a call on behalf of a customer account, the property value should be "account-id" followed by the customer account's ID (e.g., on-behalf-of: account-id <account-id>). When making a call on behalf of a Subuser, the property value should be the Subuser's username (e.g., on-behalf-of: <subuser-username>). See On Behalf Of for more information.
Comma-delimited list specifying which generations of templates to return. Options are legacy, dynamic or legacy,dynamic.
legacyPossible values: legacydynamiclegacy,dynamicThe number of templates to be returned in each page of results
1Maximum: 200A token corresponding to a specific page of results, as provided by metadata