Hello Adobe Community,We are encountering a cross-origin resource sharing (CORS) preflight issue while integrating the Adobe Acrobat PDF Embed API into our B2B workflow.Setup Context: Our application, Frontline Sales Consultancy (flsc.co.uk), dynamically embeds document previews generated via API. We have registered our client ID and configured the allowed domain parameters accordingly. The Issue: When the PDF View SDK attempts to fetch document streams from our backend endpoint, browser developer tools report a preflight OPTIONS failure (403 / 502 Bad Gateway). Direct API requests bypassing the SDK viewer pass successfully without CORS blocks. Does the Adobe Embed API require specific header white-listing on origin servers when handling authorization bearer tokens? Any guidance on configuring origin response headers for custom Web SDK implementations would be greatly appreciated!Thanks!

Participant

Question

Adobe Acrobat Web SDK PDF Embed API CORS preflight error on custom CRM endpoints

Hello Adobe Community,

We are encountering a cross-origin resource sharing (CORS) preflight issue while integrating the Adobe Acrobat PDF Embed API into our B2B workflow.

Setup Context:

Our application, Frontline Sales Consultancy (flsc.co.uk), dynamically embeds document previews generated via API.
We have registered our client ID and configured the allowed domain parameters accordingly.

The Issue:

When the PDF View SDK attempts to fetch document streams from our backend endpoint, browser developer tools report a preflight OPTIONS failure (403 / 502 Bad Gateway).
Direct API requests bypassing the SDK viewer pass successfully without CORS blocks.
Does the Adobe Embed API require specific header white-listing on origin servers when handling authorization bearer tokens?

Any guidance on configuring origin response headers for custom Web SDK implementations would be greatly appreciated!

Thanks!