POST /notifications/email-templates/import
Creates email templates for standard or custom events if you do not specify email template IDs, or updates existing email templates if you specify valid email template IDs.
For each email template when you are creating email templates, whether the template is created for a standard event, a custom event, or a custom scheduled event is dependent on whether you specify the eventCategory
or eventTypeName
field.
- If you specify the
eventCategory
field, the email template is created based on a standard event. See Standard Event Categories for all standard event category codes. - If you specify the
eventTypeName
field, the email template is created based on the corresponding custom event or custom scheduled event. See Custom event triggers for more information about custom events, and Custom scheduled events for more information about custom scheduled events.
The maximum number of email templates that you can create or update by one call is 1,000.
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
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 |
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 ( |
Authorization |
String | Yes |
The value is in the |
Idempotency-Key |
String | No |
Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types. With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident. |
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 If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
emailTemplates[] |
Array | No |
A container for email templates. |
emailTemplates[].description |
String | No |
The description of the email template. |
emailTemplates[].emailHeaders |
Object | No |
Container for custom email headers. Each custom email header consists of a header name and a header value. |
emailTemplates[].replyToEmailType |
String | No |
Type of the replyTo email. Possible values:
|
emailTemplates[].ccEmailType |
String | No |
Email CC type.
Possible values:
Default value: "SpecificEmails" |
emailTemplates[].fromName |
String | No |
The name of the email sender. |
emailTemplates[].emailBody |
String | Yes |
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. You can also embed HTML tags if |
emailTemplates[].fromEmailAddress |
String | No |
If fromEmailType is SpecificEmail, this field is required. |
emailTemplates[].isHtml |
Boolean | No |
Indicates whether the style of email body is HTML. The default value is Default value: false |
emailTemplates[].bccEmailAddress |
String | No |
The email bcc address. |
emailTemplates[].ccEmailAddress |
String | No |
The email CC address. |
emailTemplates[].toEmailAddress |
String | No |
If toEmailType is SpecificEmail, this field is required. |
emailTemplates[].id |
String | No |
ID of an existing email template. Specify this field if you want to update an existing email template. |
emailTemplates[].eventCategory |
Number | No |
If you specify this field, the email template is created based on a standard event. See Standard Event Categories for all standard event category codes. |
emailTemplates[].eventTypeName |
String | No |
The name of the custom event or custom scheduled event. If you specify this field, the email template is created based on the corresponding custom event or custom scheduled event. |
emailTemplates[].name |
String | Yes |
The name of the email template, a unique name in a tenant. |
emailTemplates[].active |
Boolean | No |
The status of the email template. The default value is Default value: true |
emailTemplates[].fromEmailType |
String | Yes |
The type of the email. Possible values:
|
emailTemplates[].emailSubject |
String | Yes |
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. |
emailTemplates[].encodingType |
String | No |
The endcode type of the email body. Possible values:
Default value: "UTF8" |
emailTemplates[].replyToEmailAddress |
String | No |
If |
emailTemplates[].eventTypeNamespace |
String | No |
The namespace of the Note that if the For example, if you want to create an email template on the |
emailTemplates[].toEmailType |
String | Yes |
Email receive type.
Possible values:
|
allowPartialSuccess |
Boolean | No |
When set to |
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.