Constituent api next_link pointing to wrong endpoint

Bruce Smith

I'd like to note this doesn't happen to all our clients, only one of our clients is affected.

First call to the Constituent endpoint:

https://api.sky.blackbaud.com/constituent/v1/constituents?include_deceased=true&include_inactive=true

the call returns next_link as https://api.sky.blackbaud.com/constituents?sort_token=ew0KIC…..&include_deceased=true&include_inactive=true

notice how the root changes it goes from /constituent/v1/constituents? to /constituents?
should we be fixing the root of the next_link ?

Ben Lambert

Hi Bruce,

This looks like a legitimate bug in the API - can you file this ticket with Blackbaud Support so that it can be tracked internally and routed to the appropriate team?

Bruce Smith

Thanks Ben, we tried to open a ticket and they sent us here. Case number 018750500