Constituent Custom Search Returns Non-Constituent Records

Marlin Integrations

We are using the below API Endpoint to find a constituent record using the first name, last name & email address. It's working fine except for an edge scenario when there are imported “constituent” records in the system with a FALSE “is_constituent” attribute value. These “constituent” records are not valid constituents therefore we are not able to allocate any gift to them.

We tried to add the “is_constituent” attribute as an extra parameter for the query however it's not making any difference

https://api.sky.blackbaud.com/nxt-data-integration/v1/re/constituents/customsearch?firstname=Jon&lastname=Smith&email=jonsmith@hotmail.com.au&is_constituent=true

Can you please advise how can exclude “non-constituent” records from the search results?

Anthony Gallo

@Marlin Integrations we do not currently offer the ability to filter the call based on constituency status. This is list related and we may be able to revisit it once our list project is complete in mid 2023.
I would question why that value is not marked true if they are in fact valid constituents. To me the user or application that is importing those records should be flipping that value if in fact those records should be full constituents.