We have implemented Target Server side using Delivery API and our website follows AEM headless architecture. Wanted to check for the below queries -
1. Will there be any usecases where we will require QA urls to preview the experience or since its server-side and headless, QA urls will not make sense.
2. Will debugging parameters like mboxTrace/mboxDebug/mboxDisable will also not be required in case of server-side and headless implementation
Solved! Go to Solution.
Hi @Gaureshk_Kodag ,
Is there any documentation on how to use QA urls in case of using Delivery API. From my observations, APIs don't return any content until you publish it so not sure how we can leverage QA urls.