Best practice for creating APIs in AEM In Java projects, one would usually use spring boot, and generate versioned apis from annotated controllers and models and use swagger to test/document. APIs would include customer login, registration, edit details, get order history etc. Some calls search and return content, e.g using sql2 and some will hit back ends behind aem. They would use Json. while we could hand write servlets which manually unmarshal and marshal request and response objects, this would be like going back to the 80s. Does aem have a recommended way to create versioned apis for the front end to consume, with built in documentation generation? I saw there is a swagger aem project, but not sure how this would work with aem not being spring or mvc i understand that aem uses sling, but I haven’t found a tutorial on how this might be used, and the sling servlet reference docs don’t seem to have a way to specify the actual type of the request and response other than as
