Addition of Communication Preference List (All constituents) entity

With the new Consents module's arrival and GDPR approaching, we'd like to be able to do some detailed reporting on Solicit Codes/Communication Preferences via the API. Without an Communication Preference List (All constituents) entity, we have to make calls to the API for every constituent using the Communication Preference List (Single constituent) to bring back this data.

  • Grant Quick
  • Feb 28 2018
Constituent API
  • Attach files
      Drop here to upload
    • Justin Beasley commented
      24 Mar 17:45

      Has there been any issue on this? We're running into the same issue with out-of-system segmentation needs and API limits.

      Attachments Open full size
    • Trent Johnson commented
      March 30, 2022 19:13

      This is a must! We aren't able to to marketing segmentation outside of RE without the ability to sync this data via API.

      Just like there's the ability to download all the constituent codes for a constituent, we need the ability to download all the solicit codes for a constituent.


      Attachments Open full size
    • Leonard Newman commented
      February 18, 2020 20:02

      Yes! How soon can we get this implemented? We need the communication preference for all constituents, not just 1.

      Attachments Open full size

    Related ideas