Status Codes in OpenApi schema should not be like 1XX, 2XX, 3XX, 4XX, 5XX
Wednesday, August 10, 2022 at 09:56amThe current OpenAPI schema https://community.onespan.com/sites/default/files/interactive_api_references/tid-api_13022020_0.json contains the following status codes for responses - 1XX, 2XX, 3XX, 4XX, 5XX for several API endpoints like these:
-
POST /orchestration-commands
-
POST /mobile-commands/**
This breaks the code generators output - see the screenshots attached.
Please consider updating OCA OpenAPI schema to use valid response statuc codes instead of pseudo integers ending with 'XX'. Thank you in advance!
Reply to: Status Codes in OpenApi schema should not be like 1XX, 2XX, 3XX, 4XX, 5XX
Wednesday, August 10, 2022 at 10:01amThe related documentation about the code generation for OpenApi / Swagger schemas on Microsoft documentation site:
NSwagStudio GUI tool:
Reply to: Status Codes in OpenApi schema should not be like 1XX, 2XX, 3XX, 4XX, 5XX
Wednesday, August 10, 2022 at 02:06pmHi Dmitry,
Thanks so much for your post! If you preferred, I'd like to fill in two support tickets on your behalf and forward these requests to our R&D team for further analysis.
Duo
Reply to: Status Codes in OpenApi schema should not be like 1XX, 2XX, 3XX, 4XX, 5XX
Thursday, August 11, 2022 at 03:30amHi Duo,
That would be great. Could you please drop here the ticket numbers? Thank you in advance!
Reply to: Status Codes in OpenApi schema should not be like 1XX, 2XX, 3XX, 4XX, 5XX
Monday, November 14, 2022 at 04:04amI totally like your gave limits as some information which is totally essential for me.
MyPayments Plus