I found this RFC referenced in the docs of a web framework (Litestar; https://docs.litestar.dev/latest/usage/plugins/problem_details.html), and found it to be an interesting take on error handling. It reminds me of an all job where the rule was that all user-visible errors must have proper documentation and instructions for the user on how to go about resolving them (even if often the solution was to contact your admin). I think the idea can apply not just to HTTP APIs. I prefer it to generic exceptions that usually describe only the immediate error (some file not found let’s say) but don’t provide enough context about where the incorrect inputs are coming from and how to resolve the issue. Comments