Feature Request

The synchronization of API endpoint order after re-arranging endpoints in the API definition within the CI/CD flow does not reflect as expected. This affects the usability and readability of the API documentation. Current Behavior: Upon initial upload of the spec file via the CI/CD flow, the endpoints are displayed in the expected order. After re-arranging the endpoint of the API definition and performing a Resync, the order does not reflect. Expected Behavior: When an API definition is modified to change the order of endpoints and a Resync is executed, the displayed order should accurately reflect the changes made in the API definition. Request: Implement a feature that ensures the order of API endpoints is updated correctly after a Resync, reflecting any changes made in the API definition.

Would it be possible to restore the option to expand/collapse the "Try it" panel in API docs? At the moment, the min width is 300px and this is very narrow. And sometimes, the request/response examples contain long strings. Other option would be to provide means to override the min width in the CSS. Testing on the webpage showed that "min-width: 500 px" looks nicer and more spacious.

Sometimes, company's customer success managers copy the response examples to our customers. It would be much easier if the response panel, too, had a copy button.

Kudos to the engineering team for the addition of OpenAPI 3.0 support. However, all of our APIs are built on the OpenAPI 3.1 spec.

In the API Documentation, the "Try it" option should be configurable where there should be an option to enable or disable for the end points based on the requirements.

It would be helpful if you could support more than 3 levels of nested categories for API documentation.

It would be nice to have some additional languages for the API documentation add-on's Try It feature. Currently the list of available languages do not include some commonly used languages. The biggest need is for PowerShell, but the others would be nice to have too. Desired languages: PowerShell NodeJS cURL PHP

The customer would like the API Documentation to be the main workspace in their project. Once they access their domain URL, it should directly lead them to the API Documentation. It would be ideal to have the option to set the main workspace as the API Documentation. Thank you.

We would like to include an option in the API documentation that requires users to authenticate each time they access our endpoints. Currently, once users authenticate, they can continue using the same endpoint for subsequent requests without re-authentication. We are looking for a solution that mandates authentication for every request made to our endpoints.