Communication Preference Post Constituent Consent List

I am building out a form to update consent for my user. They will be able to see what they currently have checked and be able to update what they have consented to. (this will tie back to solicit codes)

The issue I have is that when a user wants to update 3 or 4 consent this means I need to make 3 to 4 calls to the API plus calls to get what is currently set. The consent object is not very large and I believe that post with multiple consent should be easy for the system to consume thus reducing the amount of calls made to the API.

This could be restricted with a size limit of the JSON data being pushed.

This could be applied to other related data as well such as actions or custom fields.

  • Nick Johannsen
  • Apr 3 2023
  • Attach files