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.