TLikewise, was writing an API wrapper this morning, had to just guess and check to find error codes that I could turn into errors that conformed to our API. Not the end of the world, but if they could be included in the API docs that would be really great.
RHey there - Thanks for sharing all of this feedback, folks! In your opinions, what would you find most helpful to see in an error message?
You mentioned wanting it to be more descriptive but what exactly would be ideally shown in our error messages? @Haarolean @Luka & @Ty
And where would you want a list of common error messages to exist? In the community, documentation, or both?
You mentioned wanting it to be more descriptive but what exactly would be ideally shown in our error messages? @Haarolean @Luka & @Ty
And where would you want a list of common error messages to exist? In the community, documentation, or both?
TI would love it if in the API documentation, for any given endpoint, there was a list of the error codes that may come back and a description of what those codes meant.
RCan you share exactly which endpoint you were using in this case? Was it this? 
https://zitadel.com/docs/apis/resources/auth/auth-service-list-my-memberships
https://zitadel.com/docs/apis/resources/auth/auth-service-list-my-memberships
R@Ty
T@Raccine it was a few endpoints when I was working on building out a custom login portal. I think posting, getting, and patching sessions. Then getting and patching auth_requests. So for example calling
PATCH /v2/sessions/:sessionId to attach the users password, but with the incorrect password, rejects with an object with code 3. It would be great if those codes were listed in the documentation so we can easily enumirate them in our code and handle them in a way that conforms to the patterns of our existing API.
Rhi @Luka @Ty @Haarolean we are aware about the vague error description and we are working on it, I will get back to this topic son enough once I have more info
TThanks!