Currently when HoldingsIQ returns 429 code, /eholdings/status endpoint returns data with isConfigurationValid: false even when configuration is, in fact, valid. This prevents front-end from showing a correct error message.
In scope of this tickets changes have to be made to return semantically correct response. isConfigurationValid should be false only when it's not valid, otherwise an error message has to be returned (in case of 429 code from HoldingsIQ it's "Unable to complete operation. HoldingsIQ API limit has been exceeded. Please contact your EBSCO Holdings IQ support contact.")
Currently when HoldingsIQ returns 429 code,
/eholdings/statusendpoint returns data withisConfigurationValid: falseeven when configuration is, in fact, valid. This prevents front-end from showing a correct error message.In scope of this tickets changes have to be made to return semantically correct response.
isConfigurationValidshould befalseonly when it's not valid, otherwise an error message has to be returned (in case of 429 code from HoldingsIQ it's "Unable to complete operation. HoldingsIQ API limit has been exceeded. Please contact your EBSCO Holdings IQ support contact.")