Feature Request

Extend Eddy's functionality to API documentation

This request was created on behalf of Arroyo At this time, the method name is shown as 'PAT' instead of 'PATCH' in the category manager available in the site. It would be better if we show the complete method name. Thanks.

Currently, we won't be able to create a 2nd level sub category in Document360. But, once the user reorders the endpoints into their respective sub categories, we maintain that order on resync. We should allow users to be able to create a 2nd level subcategory, nested categories will include > symbol as shown below. YAML paths: /pets: get: summary: List all pets tags: - Pets - Pets > Details This will convert to Pets -> Details Note: This is format used by the tool we use to convert Postman collection to OpenAPI. If we go with this approach, then we will be able to support nested categories from Postman collection as well.

The tree structure (subfolders) used in the Postman collection should be preserved within Document360 API documentation within the parent folder.

This feature request proposes rendering body parameters in a tabular format to improve usability and ease of navigation when dealing with large query parameters in OpenAPI specification files.

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

It would be great if we can download API references uploaded to Doc360. It helps when the original file cannot be found and we know that Doc360 has the latest API reference.

Importing Postman JSON files is a great feature in the API Documentation. We would like to be able to also export existing APIs on Doc360 to a Postman collection so that we can start working exclusively with Postman instead of OpenAPI.

Even when an example is not explicitly declared in the JSON, Swagger is able to put one together by using the object type and the examples for each field. It would be a nice feature for Doc360's API docs.