Skip to main content
Impressive_Dolphin6424
Participant
September 10, 2026
Question

Adobe Document Embedding API blank preview error on legal claims portal

  • September 10, 2026
  • 1 reply
  • 13 views

Hello Adobe Community,

We are integrating the Adobe Document Generation API and PDF Embed API into our client portal (hdclaims.co.uk) to allow clients to view downloadable legal claim forms directly inside their web browser.

Issue Description:

When attempting to render generated PDF claim summaries using AdobeDC.View in Inline embed mode, the PDF viewer container displays a blank white box with a CORS header missing warning in Chrome and Edge developer console.

Environment Setup:

  • SDK: Adobe PDF Embed API (v2.x)

  • Domain: hdclaims.co.uk

  • Server: Nginx reverse proxy serving static PDF assets over HTTPS.

Steps Taken:

  1. Registered the client ID specifically bound to hdclaims.co.uk in the Adobe Developer Console.

  2. Verified Access-Control-Allow-Origin headers on origin server are configured to allow Adobe API endpoints.

  3. Tested direct access to PDF file path, which opens correctly outside the embedded viewer.

Is there any specific CORS or CSP (Content Security Policy) directive required when loading local PDF blobs via Adobe PDF Embed API on .co.uk domains?

Any technical advice would be appreciated!

    1 reply

    Amal Jaiswal
    Community Manager
    Amal JaiswalCommunity Manager
    Community Manager
    September 10, 2026

    ​Hi @Impressive_Dolphin6424 ,

    Hope you are doing well and thanks for the detailed writeup. Before suggesting anything, I want to confirm a few specifics, since "CORS header missing" can point to more than one place in this API.

    Could you share:

    1. The exact, full text of the console warning/error, including which specific URL or resource it's complaining about (the PDF file itself, or a different Adobe API endpoint)?

    2. Whether your previewFile() call is using location: { url: ... } to point at the PDF, or content: { promise: ... } where you fetch the file yourself and pass the binary directly?

    3. What domain the actual webpage (the HTML page with the embed script and div) is served from, as opposed to where the PDF file itself is hosted, if those differ?

    4. The current Access-Control-Allow-Origin value your Nginx config is actually returning on the PDF file's response headers right now (you can check this in the Network tab of dev tools by clicking the failed request)?

    What I can confirm the CORS issues in this API are a documented, known category of problem specifically tied to loading a PDF by URL, and Adobe's official guidance lists the same two fixes plus an alternative loading method: PDF Embed API How Tos, CORS section please give it a try and see if that helps.

    Once I have the actual header value and the exact error text, I can point to the right direction rather than guessing at which one applies here.

    Hope this information will help.

     

    Regards
    Amal

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices