Use problem+json

[ioggstream]

I suggest

Use problem+json rfc 7807, together with SOAP 1.2 faults to avoid inconsistencies in schema
and implement a global error-management strategy.

https://github.com/ongov/API-Guidelines/blame/master/API-Guidelines.md#L195

[AofH]

RFC 7807 is a good example of how an API might respond to errors. However it may not be suitable for all API's being built. I will ask the team to link out to the RFC as an good example of error handling and messages.

[ioggstream]

Great! In Italy we're trying to standardize the error semantics for HTTP APIs to address cascade failures (Eg. when a service is made up of different interacting APIs).

It's important to note that - in that case - having a consistent way to transport some failure information without disclosing implementation details (Eg. http status code, ...) become critical for that kind of services to interoperate.