📘
Your daily suppression files should only include contacts newly added to your list in the last 24-48 hours using the timestamp that represents when they were first added to your list. We recommend 48 hours in the event of an outage in your ESP platform.

👍
For a successful integration, please refer to the API guide, which provides detailed information on the rules and limitations applicable to this endpoint.

File Format

The uploaded CSV file should adhere to the following format:

Plain Text Encoding: Ensure the file is encoded in plain text (e.g., UTF-8).
One Entry Per Row: Each email address or MD5 hash should be on a new line.
Optional Header Row: The first row of the file can be a header row with column names, which will be skipped during processing.

Supported Content: Each row should contain either a valid email address or a 32-character lowercase hexadecimal MD5 hash.

Example (Emails):

email
test1@example.com
another@domain.net
user123@anothersite.org

Example (MD5 Hashes):

md5
e10adc3949ba59abbe56e057f20f883e
d41d8cd98f00b204e9800998ecf8427e
a5d4c3b7d6e0b2a1f83d7e9c5f0d9a2b

❗️
For consistent identification, ensure email addresses are converted to lowercase before generating their MD5 hash.

Your daily suppression files should only include contacts newly added to your list in the last 24-48 hours using the timestamp that represents when they were first added to your list. We recommend 48 hours in the event of an outage in your ESP platform.

For a successful integration, please refer to the API guide, which provides detailed information on the rules and limitations applicable to this endpoint.

File Format

For consistent identification, ensure email addresses are converted to lowercase before generating their MD5 hash.

200200

400400

401401