New one up πŸ—žοΈ

"Adopting Problem Details for HTTP APIs"

In which I rant a bit, but also provide a glimpse into how we're approaching it at work.

#OpenApi #HttpApi #ProblemDetails #DotNet #CSharp

https://blog.codingmilitia.com/2025/07/15/adopting-problem-details-for-http-apis/

Adopting Problem Details for HTTP APIs

Time for a quick post about Problem Details, and how we adopted it at work, in a way that’s actually useful.

Coding Militia

Anyone has built non-trivial APIs using #ProblemDetails and #OpenApi (or #Swagger, whatever you like to call it)?

Maybe it's just me, but at times it seems that they're a bit at odds. While with OpenAPI, I'd expect a more static description of the various possible errors and related properties, Problem Details feels like something more dynamic.

Now where does one document the possible types of errors and accompanying details? In an auxiliary document? Seems a bit meh...

Today I've spent some time playing with #ProblemDetails and #ExceptionHandling in #dotnet. Here some quick overview. #cocktaildev #dotnet8