Issue with next_link pagination. Returns a 404 (not found) for several customers.

Kanwei Li

We use the /gift/v1/gifts? endpoint to get a collection of gifts. We use the next_link property in the response to query the API again for more gifts. It has always worked out well, but we have several customers in our portfolio where it breaks. Re-querying the API with next_link returns a 404 (not found). I was wondering if anyone else is experiencing this?

Kanwei Li

I'd like to confirm that I found a bug in the API (Im like at least 95% sure of it)

For customers who are broken, the next_link has a root url of

“https://api.sky.blackbaud.com/gifts?”

for customers that are not broken, the next_link has a root url of

“https://api.sky.blackbaud.com/gift/v1/gifts?”

We added more logging to our app and saw that pattern.

I was wondering if it would be possible if you all fix that within a reasonable amount of time? If not, do you recommend that we update our software to detect bad root urls and replace them with good roots?

If you all need more information with Blackbaud IDs of affected customers, please let me know and I'll submit those in a private thread.

Anthony Gallo

This looks buggy for sure. Can you let me know what environment ID you are running your calls against? Feel free to email me that info instead of posting it here.

Kanwei Li

Thanks Anthony - it's actually happening to 15 customers in our portfolio. I'll email the environment ids shortly.

Anthony Gallo

I am going to post the reply here because it does involve a fix on our side that I wanted to document for future reference. The issue was with one datacenter that hosts those environments. We found the issue and it should be working as expected now. Please give it a try and let me know if you are good to go.

Kanwei Li

Ya, I think we are in good shape now Anthony - definitely do appreciate your prompt response. Take it easy!

Anthony Gallo

Good to hear!