Ability to access primary addressee/salutation data in bulk
The primary addressee and salutation are necessary when communicating with constituents, for example Dear [Mr & Mrs Drake].
Currently they can be accessed on a per constituent basis via this endpoint:
This causes huge problems when synchronising with our internal reporting/selection system.
We have to call a list of all constituents that have changed in any way at all, then for each one get their salutations (whether their salutations have changed or not!). This is very inefficient and causes us to make thousands of unnecessary API calls.
Solutions
Preferred: Include the primary addressee and primary salutation fields in the constituent entity for both 'GetConstituents' and 'GetConstituent'.
Acceptable: Create a GetNameFormatSummaryList endpoint where we can get them for all constituents.
-
James Phillips
- Jan 10 2022
Has there been any progress here? I see on this thread that Anthony Gallo said:
"We are doing a lot of backend plumbing work in our lists infrastructure to help with getting some of these much needed fields added later in the year."
. . . that was back in January 2023.
We need to be able to to pull this for out-of-system mail selects, but getting these on a per-constituent basis would take tens of thousands of API calls, and we'd have to regularly re-pull them to get changes.
For now, I would even settle for getting the Name Format ID so I could re-merge these myself from the pattern.
Has there been any movement on this? When we pull data from the Sky API to produce a file for mail merge, we need to have the donor's salutation.