In a perfect world we would love to send you an JSON object containing the new lists name and an array of all the constituent IDs. We wouldn't need this new feature to find constituents by name, we would feed the constituent IDs directly to the API endpoint. Something like this maybe:

POST https://api.sky.blackbaud.com/lists/v1/list

{"constituants":[10031,10602,10032,10268,10211,10033,10192,10170,10279,10276,10161,10416,10272,10203,10153,11150,10312,10358,10340,10035,10036,10137,10112,10172,10037],"name":"listName"}

We currently curate static lists in our FileMaker-based solution. We have lists of 25 people and we have lists of over a thousand of people. We'd like the option to add as many constituents as possible, that way we could even send/add constituents in batches.

NYSCF uses static lists daily for several different kinds of tasks. I would imagine that eventually they will learn to favor the dynamic lists avail to them in RENXT, but for now, they can't even consider that a list of constituents would change without their having done so. Some examples of how these lists are used on a daily basis:

• Batch add "actions" or "notes" to a group of poeple

• Invite a certain lists (lets say "List A" and "List B") to one event, then invite "List A" and list "C" to a different event. It's not usually as simple as inviting the same people as last time. For our larger events it is though.

• We build lists of people we want to email blah about something. While that email is being written/designed, the list of people is curated in advance and VERY OFTEN that list is started by our CEO and/or another member of our board and then the NYSCF staff will add to the list

• You'll see that we use static lists often as our relationship to our constituents is close and it's not as simple as "everyone who gave more than X and also has an interest in Y.....

Currently NYSCF will create a blank list and then add contacts (constituents) as time goes by. For a number of reasons. Sometimes the list will be created from a found set of constituents or from a paper list given to NYSCF staff by leadership etc....

There is no current way to import static lists dugin our conversion. We spoke at length with the the fabuous Marcello Maroto and David Burger.

TBH it took several times explaining to David that we need to import "static lists". Several times he interpreted that to mean we wanted to import new contacts that we had on a static list/spreadsheet. He was well intentioned but was not understanding until after an hour on the call with him. He also tried to show us how to build static lists in db view as well as RENXT. Again, not what we were assign for.

Another solution that was proposed to us was that we could import our over 7,000 static lists as events and then convert them into static lists. This was an option, but it makes really messy event data. If we then wanted to "clean up" the mess, we would have to go back and one at a time delete the over 7,000 events that were created for the sole purpose of getting our static lists into RENXT.