Import suppression entries
Adds up to 1,000 entries to the do-not-contact list in one request; values already on the list are left unchanged.
Normalization and matching are the same as POST /v2/sequencer/suppression.
A value already on the list is left exactly as it is: its reason is not overwritten and no duplicate is created, so replaying the same list is safe. A value that is empty once normalized (a blank value, or a phone value with no digits) is returned in skipped with the reason empty after normalization, and the rest are imported. imported counts every row now on the list, including rows that were already there.
New entries are recorded with source: import. Acts as user_id. Counts against the Sequencer writes rate limit.
Handling the response
imported counts every row now on the list, including values that were already there. skipped lists rows that were empty once normalized, such as a phone value with no digits.
Good to know
- Values already on the list are left exactly as they are, so replaying the same file is safe and does not change their
reason. - Each value is normalized and matched the same way as Add a suppression entry.
- For more than 1,000 values, send batches of 1,000.
Authorizations
Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.
Headers
Makes this write safe to retry. Send a unique value, such as a UUID, and send the same value again when you retry the same request. A retry with the same key and the same request (method, path including the query string, and JSON body) returns the original successful response without acting twice. The same key with a different body or path returns 409, and so does a retry while the first request is still running; that one is safe to repeat after a moment. A request that fails frees its key, so a retry runs the write again: after a 5xx on a create, confirm with a GET before retrying. Keys are kept for 24 hours and are scoped to your team.