Relation between JobRequest and Account

Overview

Some of Transactional Email features can be controlled at both JobRequest level or at Account configuration level. If JobRequest flags have been meant to provide granular control over which message must enable a feature or not, on the other hand the Account configuration has been designed to allow or not the usage of a feature, and define the default expected behaviour for every JobRequest.

At the Account level you can ask for each feature to set the following values:

• active: define if the feature is authorized to be used with the account or not;

• defaultActive: define the default expected behaviour if nothing is explictly set into the JobRequest sent to that Account (see below).

If the feature flag is explicitly defined at the JobRequest level (true or false), it overrides the Account defaultActive configuration.

Sum up tab

*flag could be X-Header or a REST parameter

Features list

List of features that can be controlled at the JobRequest level:

• Open Tracking (REST only)

• Link Tracking (REST only)

• AntiVirus Multiscan

• Secure Document Handling (REST only)

• Message Signing

• Trace & Recover (SMTP only)

• Push Notification