PUT /notifications/email-templates/{id}

Updates an email template. This operation supports updating the email template for all event types.

Servers

https://rest.test.zuora.com
https://rest.sandbox.na.zuora.com
https://rest.apisandbox.zuora.com
https://rest.na.zuora.com
https://rest.zuora.com
https://rest.test.eu.zuora.com
https://rest.sandbox.eu.zuora.com
https://rest.eu.zuora.com

Path parameters

Name	Type	Required	Description
`id`	String	Yes	The ID of the email template to be updated.

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`Content-Encoding`	String	No	Include the `Content-Encoding: gzip` header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.
`Zuora-Track-Id`	String	No	A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (`:`), semicolon (`;`), double quote (`"`), and quote (`'`).
`Authorization`	String	Yes	The value is in the `Bearer {token}` format where {token} is a valid OAuth token generated by calling Create an OAuth token.
`Zuora-Entity-Ids`	String	No	An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header.
`Zuora-Org-Ids`	String	No	Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header. The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails. If the header is not set, the operation is performed in scope of the user's accessible orgs.
`Accept-Encoding`	String	No	Include the `Accept-Encoding: gzip` header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response. If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a `Content-Encoding` header with the compression algorithm so that your client can decompress it.

Request body fields

Name	Type	Required	Description
`description`	String	No	The description of the email template.
`emailHeaders`	Object	No	Container for custom email headers. Each custom email header consists of a header name and a header value.
`replyToEmailType`	String	No	The type of the reply email. Possible values: `"SpecificEmail"` `"TenantEmail"` `"RunOwner"`
`ccEmailType`	String	No	Email CC type. When the base object for the event is associated with `Account`, `ccEmailType` can be any values in the enum list. When the base object for the event is not associated with `Account`, `ccEmailType` must be `TenantAdmin`, `RunOwner`, or `SpecificEmail`. Possible values: `"InvoiceOwnerBillToAndSoldToContacts"` `"SoldToContact"` `"TenantAdmin"` `"InvoiceOwnerAllContacts"` `"InvoiceOwnerBillToContact"` `"BillToAndSoldToContacts"` `"InvoiceOwnerSoldToContact"` `"AllContacts"` `"RunOwner"` `"SpecificEmails"` `"BillToContact"` Default value: "SpecificEmails"
`fromName`	String	No	The name of email sender.
`emailBody`	String	No	The email body. You can add merge fields in the email body using angle brackets or double curly brackets. For more information, see Merge field syntax for email templates. User can also embed html tags if `isHtml` is `true`.
`fromEmailAddress`	String	No	If fromEmailType is SpecificEmail, this field is required
`isHtml`	Boolean	No	Indicates whether the style of email body is HTML.
`bccEmailAddress`	String	No	Email bcc address.
`ccEmailAddress`	String	No	Email cc address.
`toEmailAddress`	String	No	If toEmailType is SpecificEmail, this field is required.
`name`	String	No	The name of the email template.
`active`	Boolean	No	The status of the email template.
`fromEmailType`	String	No	The type of fromEmail. Possible values: `"SpecificEmail"` `"TenantEmail"` `"RunOwner"`
`emailSubject`	String	No	The email subject. You can add merge fields in the email subject using angle brackets or double curly brackets. For more information, see Merge field syntax for email templates.
`encodingType`	String	No	The endcode type of the email body. Possible values: `"EUC_JP"` `"UTF8"` `"X_SJIS_0213"` `"Shift_JIS"` `"ISO_2022_JP"`
`replyToEmailAddress`	String	No	If replyToEmailType is SpecificEmail, this field is required.
`toEmailType`	String	No	Email receive type. When the base object for the event is associated with `Account`, `toEmailType` can be any values in the enum list. When the base object for the event is not associated with `Account`, `toEmailType` must be `TenantAdmin`, `RunOwner`, or `SpecificEmail`. Possible values: `"InvoiceOwnerBillToAndSoldToContacts"` `"SoldToContact"` `"TenantAdmin"` `"InvoiceOwnerAllContacts"` `"InvoiceOwnerBillToContact"` `"BillToAndSoldToContacts"` `"InvoiceOwnerSoldToContact"` `"AllContacts"` `"RunOwner"` `"SpecificEmails"` `"BillToContact"`

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.