Response Codes

HTTP Response Codes

The EBSCOhost Entitlement API returns an HTTP response code with each request. The API uses conventional HTTP response codes to indicate success or failure of the request. Response codes in the 400 range indicate an error in the information that was provided in the request. For example, a 404 HTTP response code is returned by the service if the information provided is missing a required parameter. Response codes in the 500 range indicate an error on the server, a database error or an API settings error. The HTTP response codes are below.

Response Codes

CodeTextRetryDescription
200OKYesEverything worked as expected.
202AcceptedYesThe request has been accepted for processing, but the processing has not been completed.
204No ContentYesThe server has successfully fulfilled the PUT request and there is no additional content to send in the response payload body.
400Bad RequestNoThe request could not be understood by server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
403ForbiddenNoThe request is understood but access is not allowed due to the IP whitelisting policy.
404Not foundNoThe URI requested is invalid. Also returned when the requested format is not supported by the requested method.
409ConflictYesThe request could not be completed due to a conflict with the current state of the resource.
429Too Many RequestsYesReturned when a request cannot be served due to the application’s rate limit having been exhausted for the resource.
500Internal Server ErrorYesSomething is broken. Try again later or you may contact the EBSCO customer service team at [email protected].
503Service Unavailable ExceptionYesOur servers are up, but overloaded with requests. Try again later or you may contact the EBSCO customer service team at [email protected].
504Endpoint Request Timed-out ExceptionYesOur servers are up, but the request couldn’t be serviced due to some failure at our server. Try again later or you may contact the EBSCO customer service team at [email protected].