Call for a better Error Handling in APIs

There are use cases where a 3rd party system returns something that can’t be defined as a clear error, but returning a http status code of 200 OK is also wrong. For those cases, every vendor has its own way of communicating to the client what has gone wrong in the backend. So depending on the microservice you want to integrate into your system, you will have to work with very different ideas of how errors are being communicated back to you. This is why we need to find a common way to communicate those edge cases.

André Cedik has worked for more than 15 years in the eCommerce field and is now developer advocate and software developer at shipcloud to help developers to integrate the shipping service provider into their online shop, erp system or software solution.