Receive 500 Server Error if User ID is not found

Steven Cinquegrana
Steven Cinquegrana
Tenth Anniversary Kudos 2 Name Dropper Participant
in Education Management APIs

In both our own SKYLib•NET code and via the Endpoint Reference Try It, we're seeing 500 Server Error responses if the call is made with an invalid/non-existant User ID:

Eg

{ "type": "urn:blackbaud:unexpected", "title": "An error has occurred.", "status": 500, "trace_id": "63a13120968e41a19ea497fa1547ec67", "span_id": "0ef9fff7e9e8fa48" }


I would expect a parameter-type error - a 400 or a 404 - rather than a 500. Throwing a 500 in this situation can trigger a wait on an outage to resolve rather than signalling an out-and-out failure which should not be retried.

Can this be looked at please? Throwing a 500 Server Error should be the response of last resort.

Thank you.

Steve Cinquegrana | CEO and Principal Developer | Protégé Solutions

Comments

  • Jared Harbour
    Jared Harbour Blackbaud Employee
    Eighth Anniversary Kudos 1 Name Dropper Participant

    Hi Steven,

    I took a look at the endpoint above and I have confirmed that when a user-id doesn't exist the call results in a 500 error response. I agree this is not a good option and we will work on getting this fixed as soon as possible.

    Best,

    Jared

Categories