Managing API errors

APIs are the main source of headaches in the project. API calls happen through the network and the potential for failure always exists. The API could respond differently based on the status of the response, and other scenarios could occur, such as the server being down, unhandled exceptions occurring while processing the request, or authentication and authorization errors.

For all these reasons, it’s very important to handle API requests carefully. The starting point is to understand at each point what could go wrong and what the appropriate response is in each case. If you are the developer of the API, things are easier, but if you are not, the documentation should be the main source of truth.

The BooksStore API has the Swagger page that we used in previous chapters to understand the input and output of some API endpoints. We noticed that the endpoints either succeed or retrieve the 400 Bad Request status code, which means something went wrong on the...