Emarsys

Authentication & Authorization

Credentials

• Emarsys connects via WSSE authentication.
• WSSE authentication requires a custom X-WSSE header for each request.
• The X-WSSE header is generated from API user name and secret, that can be created in the Emarsys dashboard. See Emarsys Connection Instructions.
• Publicly exposing your API secrets can allow unauthorized access to the Emarsys API endpoints, and your Emarsys data by a third party. DataGrail stores your API secrets encrypted and protected.

Permissions

API permissions should be assigned a user to limit DataGrail access to certain Emarsys API calls. See Emarsys Connection Instructions.

The next permissions are required and should be set to connect DataGrail integration:

• contact.getdata – return the field values of the contacts specified by either their internal identifiers or by a custom property;

Additionally, depending on the required integration capabilities, DataGrail requires the following permissions to be set:

Access

• field.get – generate a list of the available contact fields.

Deletion

• field.get – generate a list of the available contact fields;
• contact.delete – delete contact.

Transaction Mailer

• campaign.broadcast – send emails using API to trigger an external event.

Endpoints Utilized

DataGrail uses the following endpoint to verify API connection:

• POST https:​//api.emarsys.net/api/v2/contact/getdata

Version

DataGrail Emarsys integration currently supports API version 2 (v2).

Limits

DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

Access

For an access request, DataGrail will take the following actions:

• Get Contact Data by the Data Subject email.
• List Available Fields to get available field names.
• For all objects found, DataGrail will return all available fields. You can edit which objects and fields you want to provide to the Data Subject via our Portal Requests.

DataGrail also supports the Direct Contact Access workflow for Emarsys.

Endpoints Utilized

• POST https:​//api.emarsys.net/api/v2/contact/getdata
• GET https:​//api.emarsys.net/api/v2/field

Deletion

For a deletion request, DataGrail will take the following actions:

• Get Contact Data by the Data Subject email.
• List Available Fields to get available field names.
• Delete Contacts by the Data Subject email.

DataGrail also supports the Direct Contact Deletion workflow for Emarsys.

Endpoints Utilized

• POST https:​//api.emarsys.net/api/v2/contact/getdata
• GET https:​//api.emarsys.net/api/v2/field
• POST https:​//api.emarsys.net/api/v2/contact/delete

Transaction Mailer

Emarsys integration can be configured as DataGrail Transactional Mailer.

In this mode, DataGrail uses Emarsys integration to send emails as broadcast events, using pre-configured mail stream with uniq Campaign ID (see Emarsys Connection Instructions).

Endpoints Utilized

• POST https:​//api.emarsys.net/api/v2/{campaignId}/broadcast