Specify additional known responses other than 200 OK in swagger schema

[thhermansen]

Tripletex's schema describes 200 OK responses, like this:

but it is lacking in regards to describing the other expected responses like 401, 422 etc. This results in generated clients¹ not knowing of all responses an operation may yield, in this case it has no knowledge of any errors:

If I understand swagger's doc² correctly it would be appropriate to include other common responses too:

Note that an API specification does not necessarily need to cover all possible HTTP response codes, since they may not be known in advance. However, it is expected to cover successful responses and any known errors. By "known errors" we mean, for example, a 404 Not Found response for an operation that returns a resource by ID, or a 400 Bad Request response in case of invalid operation parameters.

Footnotes

1. Example https://openapi-ts.pages.dev/ ↩

2. https://swagger.io/docs/specification/2-0/describing-responses/: ↩