Could we add constituent_code filters to other endpoints?

Dan Bonville

Hello,


We use the Constituent API and rely upon the constituent_code filtering available in the constituent list endpoint to narrow down to the constituents we "care" about.  We also pull information from other endpoints (education, relationships, etc.).  However, we can't use constituent_code to filter on those endpoints.  This leaves us with the decision to:

a) Pull all the data for all constituents whether we need it or not via the "all" endpoints, which leaves us with mountains of cruft data

or

b) Make a ton of calls for each individual constituent which will quickly tax our quota of calls


If we could filter on constituent_code in these endpoints, it would make me so so so happy and I am sure would be greatly useful for other SKY API users.  


Thanks,

Dan


P.S. I will throw you guys a raging pizza party with beer and chicken wings if you add this to the API.

Dan Bonville

I just wanted to follow up on this one and see if there are any other developers feeling the pinch from this one.


Because there is often a large amount of cruft data in addresses/relationships/etc. I feel adding filters to these endpoints would offer a vast improvement for how we handle initial loads of data where we run into issues most often.  We can't really look at pulling each user's data individually from these endpoints as even a small number of constituents could cause us to make many calls which would end up running us into rate limits.


Being able to add constituent_code filters to other endpoints would greatly reduce the amount of data we'd need to pull and sift through and collate.


Alternatively being able to expand the data returned in the constituents endpoint could also be a great way to simplify that process.


Dan