Response 401 undocumented in Swagger
Options
Bas van Ginkel
Member ✭
Hi there,
small issue. In any flow I can use a precondition to check anything I want and cause an error to be generated. One of the error types available is the UNAUTHORIZED type. This causes the 401 response code.
This code however isn't documented in the swagger documentation. That documentation only covers 200, 400, 403, 404, 429 and 500.
My front end developer picked up on this as he ingests the swagger json to generate typescript and it was throwing an error.
Tagged:
Comments
-
Hi @Bas van Ginkel! 👋
Thank you for bringing this up. I quickly tested this and got the 401 error on the server response section. I see where it says undocumented and see that it doesn't show up with the rest of the codes. I'll check on this and get back to you.
Categories
- All Categories
- 53 ? Announcements
- 47 ? Releases
- 37 ? Welcome
- 983 ? Help! I'm a Noob
- 125 ? No-Code Front-Ends
- 633 ? Working with APIs
- 439 ? Transforming data
- 126 ? Connect Xano to ...
- 50 ?? Find an Expert
- 348 ❓Other questions
- 35 ? Security
- 22 ✂️ Snippets
- 19 ? Showcase
- 7 ?️ Xano Chatter
- 62 ? Video Tutorials
- 171 ? Request a feature
- 229 ? Report a Bug
- 19 ? Templates & Extensions
- 7 ? Feedback