Skip to content

Unsubscribe status after deleting a subscriber or list, and API blacklist endpoint

evamarrezevamarrez
edited July 24 in Questions

Hi,

I would like to clarify how Sendy handles unsubscribed users in the following scenario:

  1. A user unsubscribes from a list.
  2. The user is later deleted from that list, or the entire list is deleted.
  3. The same email address is then added to a different list.

Will the user remain marked as unsubscribed, or will they appear as active again in the new list?

My preferred behavior is for the user to remain unsubscribed, regardless of whether the original list or subscriber record has been deleted.

I also think it would be useful to add an API endpoint that allows an email address to be added to the blacklist. This would make it possible to automatically blacklist users who unsubscribe, in addition to marking them as unsubscribed from a specific list.

Is this currently possible, or is there a recommended way to implement this behavior?

Thanks.

Comments

  • BenBen

    Hi,

    Here is how Sendy currently handles this scenario and the options available:

    1. Unsubscribe Behavior Across Lists

    • List-Specific Unsubscribes: Unsubscribes in Sendy are list-specific by default. If a user unsubscribes from List A, they are marked as unsubscribed for List A only.
    • Deleting Records/Lists: If you delete a subscriber or an entire list, those records are removed from Sendy's database. If you later re-import or add that email address to List B, Sendy treats it as a new entry and sets its status to Active in List B.

    2. Global Blacklist (Suppression List)

    • To ensure a user remains unsubscribed across all future lists, even if their original subscriber record or list is deleted, their email address must be added to Sendy's Blacklist > Suppression List

    3. Current API Limitations & Workarounds

    • Currently, Sendy does not offer a native API endpoint for adding emails directly to the Global Blacklist/Suppression list (the existing API only handles list-specific actions like subscribe, unsubscribe, delete, etc.).
    • Workarounds:
      • Direct Database Entry: If you manage your own server, you can programmatically add emails directly to the suppression_list table in Sendy's MySQL database.

    Hope this helps clarify things!

    Best regards,
    Ben

This discussion has been closed.