Questions

Hi, We are using Adobe PDF Embed API, amazing free library! We have one problem.We are showing all the pdf in read only mode without annotation panel. We need to put a button beside the document name when the library finishes loading the file. We have the our div, but it can not be added to the UI using the `insertAdjacentElement` method! we are getting the span element which contains `document name` and we are trying to add our div beside it! It fails because the content which was loaded by the adobe library made browser to not insert the content in the DOM and that is why we receive null! If we open the developer console and inspect the content that adobe inserted for the pdf viewer then it will not be null. I suspect that it is because of the `role=presentation` of the content, but how we can get the pdf embed library to load the content into the dom so we will have access in Angular to add our div?

We have successfully set up a reverse proxy on our server to the main.js file. (to get around security blocking sofware) We can now pull in the Adobe PDF embed API js file in the following url: https://dr-www.mfs.com/view-sdk/main.jsHowever the PDF component starts to appear on the page but fails to complete rendering. After reviewing the developer console, it appears that there’s a JSON web token that fails to load? Is this connected to passing the client API key back to Adobe? Is there a workaround for this issue?  

Is there a way to change the default link behavior when embedding a PDF? We have a webpage with an embedded PDF that contains links to different pages on our website. When you click a link, a white box appears confirming you want to Open Web Page. After clicking the Open Link button, Microsoft Edge shows the Pop-up blocked message. That's it. Sure I can personally click to allow the popup, but that is not ideal for most of our users.

I had written about Liquid Mode for Adobe API in September and would like to know if Adobe has plans to bring the liquid mode to Adobe Embedded API as the current embedded API is not responsive for other devices.  Also, would it be possible to let me know if Adobe Embedded API have an impact on SEO?

I'm trying to extract data from a PDF using Extract PDF API. I got authorisation, submission and polling working fine. However, polling returns a broken file with a JSON in the midst of it. I'm not sure how to get rid of the broken parts and just return a JSON with the text from the PDF. Has anyone faced an issue like that?Unfortunately, I can't attach the real file because the forum won't let me.

Hi all, I'm hoping someone can help me here. I'm trying to automate a process that involves taking the output from an Illustrator script and using it fill a word template using Document Cloud. Does anyone have experience making a call to the Document Cloud API from an Illustrator script (I am currently scripting using Javascript)? What am I trying to do: Step 1 – Use an Illustrator script to output artboards as jpegsStep 2 - Insert those jpegs into a Word templateStep 3 - Output filled template as PDF to same location as jpegs so it can be zipped with the Illustrator file Any suggestions/pointers are hugely aprreciated.  

HiWe are using Adobe PDF Embed API to annotate in the PDF.We want to include Rectangle shape to draw the shape in PDF. Need to add another control beside annotation tools. How can i customize this,can you please help me on this.  

In one of the examples for the PDF Extract API, some of the text is included in a png along with the adjacent image. The text is not present in the structuredData.json file, so it is essentially not being extracted.      Is this a common issue with the Extract API? 

Hi together,From time to time we see some Internal Server errors from the Adobe API endpoint for converting DOCX to PDF or PDF to DOCX.For example multiple conversion from PDF to DOCX failed with an Internal Server error on 2021-10-28 in the times from 12:42:00 UTC till 2021-10-28 14:24:00 UTC and also later that day from 19:16:00 UTC till 19:26:00 UTC.In addition we encountered multiple Internal Server errors for the conversion from DOCX to PDF this morning at 06:54:00 UTC.Could you maybe help us understand what is causing these Internal Server errors and if there is anything on our side that we could change ?If it would help debuging the issues we could provide you the request ids of the failed conversion operations. Note: This has happened without enabling the options reported in  https://community.adobe.com/t5/document-services-apis-discussions/facing-internal-server-errors-on-pdf-services-api/m-p/12475683 that lead to all requests fail with an Internal Server error.&nbsp

The documentation indicates the PDF Embed API is completely client-based but I don't see it clearly stated whether it's 100% JavaScript (a la Mozilla PDF.js)  or whether it may utilize a PDF engine built-in to mobile or desktop operating system or browser (such as the PDFium-based viewer in Chrome Android). I'm assuming it is pure JS with no client PDF engine dependencies - is this correct? If so is the total download size comparably sized to PDF.js (32MB)?  Are there performance expectations vs. PDF.js?

I saw docs but I don't find type of embed api sdk lisence. Is it MIT? And how do I manage sdk version because the sdk is only provided from https://documentcloud.adobe.com/view-sdk/main.js Is there any plan to register npm or provide versioning endpoint?

Hello! Just a newbie here, I'm trying to play with this sample:https://codepen.io/practicalPDF/pen/dyGBQqJ Is it possible to show annotations from other users instantly (like the sample above) but using a different browser instead of in the same page? Hope the gurus notice my question. Thanks in advance!

Hi there,  We've been using the PDF Services API for the last 2 days and we still do not see any data under the Insights page in adobe.io. Screenshot attached. We know that we are using the API based on our own data, could you help us find out why this is not showing on Adobe side? We are using pay-as-you-go-licence, managed by AWS.  Thank you! 

I have tried to use the code in Dreamweaver but i get the message File preview not available - the application domain is not authorised to use the provided PDF Embed API Client ID.  I am using <YOUR_CLIENT_ID>.  I have tried a registered client id but this gets the same error. 

Hi, We are using Document Cloud SDK PDF Embed API in Production for displaying pdfs in Adobe SDK pdf viewer. It was working fine in the browsers but recently we observed that it has stopped working on Windows 10 Internet Explorer 11 and is displaying the message as "This tool no longer works on Internet Explorer due to end of support.". The screenshot is attached herewith. Please find the same. Is there any fix provided by Adobe Document Cloud SDK for this issue? Is there any alternative way to fix it on IE?This issue is in PROD. Immediate help will be highly appreciated.  Regards,Umair.

Hi, I'm a developery and I want to extract Rich Media from a given PDF file. I see that adobe has an API for extracting elements but I don't see any section for extracting Rich Media in PDF Extract API documentation.  Can anyone point me in the right direction? It would be much appreciated. Thank you and have a good day.

Hi all, I use Extract API, i wanted to know if i can mention number of pages while calling the API,for example : I want to run services for pages 50-100 in 10,000 page document. Is something like this possible?

Hi all, I'm trying to get my node.js app to generate a PDF of a table with some data on it.I am using createPdfFromDynamicHtml.My data got successfully rendered, but not their row color.  row.style.backgroundColor = `green`; This results in: Notice that the my bootstrap rounded edge style at <th> is poorly applied also. It seems to me that the parser is somehow taking a snapshot earlier than it should? Here is a snippet of where I put my code in index.html </head> <body class="spectrum spectrum--medium spectrum--light" onload = "initial()"> <script src="./json.js"></script> <script type="text/javascript"> function initial() { var document = window.document;  When looking at index.html in a browser, the rows are colored as intended.

Is there any configurations regarding the ability to reply on comments in annotations?I want to just view the annotation without being able to add a reply on clicking on it in PDF Embed API.

I am trying to preview PDF from CDN that uses dynamic URLs to generate PDF, like this:cdn.domain.com/12345/?name=filename.pdfwhere also cdn.domain.com/12345/works fine.Any workaround to this problem, or it is just not capable to read PDFs form URL that does not follow standard format (e.g. domain.com/filename.pdf) ?

For the comments, we want to do our own commenting, we have code as following:annotationManager.registerEventListener(function (event) {console.log(event);console.log(event.type, event.data);if (event.type === 'ANNOTATION_MODE_STARTED' && event.data === 'freetext') {//Do our own stuff//Is there a way to stop the default comment function?}});We basically want to use our own comment function instead of the function provided by API. We can have our comment section shows up, is there a way to stop the default comment function?

If one PDF document has annotations by many users, is there a way to disable editing/deleting annotations which are not by curent user? In other words, user should only be able to edit/delete annotation made by him/her. 

I am using the PDF extract API for one of my applications. Each PDF file page length may differ from 300 - 1000 pages. In the documentation, it is mentioned that non-scanned PDFs are limited to 200 pages and Scanned PDFs must be 100 pages or less. Limits may be lower for files with a large number of tables.To solve the above-mentioned limitations a PDF file should be split into multiple chunks, but how can I determine the optimal no. of page length for each PDF to automate the process? Questions?What is the max no. of pages that I can hit the API with a PDF which contains onlyscanned pages in it? large tables?scanned large tables? Thank you! 

We are a small media publishing website. We have tested the embed function of adobe using this: https://documentcloud.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf It works great, and we would now like to utilize this in our website. We just want to publish pdfs, and we dont need anyone to be able to sign or fill in a form, just embedding documents using iframe. What product do we use for this, and how to we upload, get started? Thanks!

I am getting 403 errors when I attempt to access the PDF Extract API using R (specifically the httr package). The API works fine in Postman, and I have successfully used the following R code to generate a "Bearer" token: r = POST( url = "https://ims-na1.adobelogin.com/ims/exchange/jwt/", body = list( client_id = {{Placeholder for client_id}}, client_secret = {{Placeholder for client_secret}}, jwt_token = {{Placeholder for jwt_token}} ), encode = "form" ) access_token = content(r)$access_token Authorization = paste("Bearer", access_token) The "Bearer" token that I have generated using R works fine when I copy and paste it into Postman for posting a PDF file and getting the extracted JSON data. So far, so good. But I get a 403 error if I try to use the same "Bearer" token (and my client_id) to get the same extracted JSON data into R using the following R code:httr::GET( url = "https://cpf-ue1.adobe.io/ops/id/{{Placeholder for x-request-id}}",