Questions

I can view them in Acrobat there are no restrictions or passwords. I can also merge the PDFs with the Edge browser. Is there another protection I should be looking out for? For context the documents that always fail are university transcripts. 

Hello all,I'm trying to simply Merge an array of 3 dynamic PDFs from Sharepoint, but when it comes to the Adobe Merge PDFs action, it simply stalls out and does not work - what am I doing wrong? Any guidance here would be very much so appreciated! I've been following these two resources:https://blog.developer.adobe.com/merging-documents-using-microsoft-power-automate-69a68e46081bhttps://community.adobe.com/t5/acrobat-services-api-discussions/merge-pdf-power-automate/m-p/14347140to no avail, sadly.

Hello all, I am encountering an issue when using MergePDF Power Automate step. So far, I have followed https://blog.developer.adobe.com/merging-documents-using-microsoft-power-automate-69a68e46081b.     Below is The results of testing my flow with the error "CORRUPT_DOCUMENT: The input file appears to be corrupted and cannot be processed" Here is also a snippet of the parameter input. I see that the files are sent as Base64 encoded. I decoded these and am able to view the PDFs which tell me they are valid documents.  parameters":{"Files Array/outputFileName":"merged.pdf","Files Array/files":["[{\"$content-type\":\"application/octet-stream\",\"$content\":\"JVBERi0xLjcNJeLjz9MNCjc1IDAgb2JqDTw8L0ZpbHRlci9GbGF0ZURlY29kZS9GaXJzdCAxOTUvTGVuZ3RoIDQxOC9OIDI3L1R5cGUvT2JqU3RtPj5zdHJlYW0NCmjenFXbahsxEP2V8wcrjWZ0gZCHkvYlNATHb6EPbipCwekGY0P995nVbBJDssXqgziLdM7MaC5aCnCghJxAGcSE4EHFI+gXM0JAKLoYPJ0JOBeECNEVEiTrWUYMTmmIKYMdEkWwR0oqImQicFAHTk2g+AQWlBTAEd6pfU6K6oMz

I have researched this error everywhere.  I am using this https://pdf-services.adobe.io/assets to get the ready made uri for the call to AWS.  If I issue this in postman I get a 200.  If I take the exact same approach in code, I get the error listed in the title and a 403 error.  I am using a PUT, and as far as I can tell everything else is identical.  If I change one character of the signature in postman call I get exact same error.  Please help this is frustrating! <Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>ASIAWD2N7EVPH76T5FGM</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256 20230329T160506Z 20230329/us-east-1/s3/aws4_request bb7eb9cce071555e8c2591a203acd3b54c6251436155ea16dbb9d6f281df4a34</StringToSign><SignatureProvided>2690325a30b45cff4b8d0

Amazon Marketplace informed us that we went over budget on April 2026 on PDF Services API.According to AWS we made over 60,000 Units (MP:Doc_Transactions-Units) on that month and racked up $3,000 in charges for PDF Services API.This is not an insignificant amount of money were talking about, so I think some actual help from Adobe is warranted.Please contact me: matias.ruiz@fastiep.com

Amazon Marketplace informed me I went over budget on May 23rd on Acrobat Services API. I usually have a ~$5.00 montly bill for document OCR that is integrated into one of my personal utilities.  According to AWS I made over 40,000 calls on that day alone and racked up $2200 in charges for Acrobat Services API.   First thing I do is go check the logs on my utility that uses this integration to see if something has gone terribly haywire.. Nothing. It actually hasn't been invoked in weeks (normal). Next up I open a ticket on AWS, and the head over to Adobe support. After going round and round with chat agents, you find out that they are not trained in API at all.. As far as the chat agents were concerned, I didn't even have an account.  In the end, the guy just told me to take it up with Amazon, and they would issue a refund.. Now another day has gone by and Amazon has responded to the ticket I opened there, and (spoiler alert).. they say it's not their

Hola, necesito ayuda con la cancelación de un plan de estudiante, o cambio de plan, debido a que ya cumplí un año en el plan normal y ahora me están cobrando el plan premium sin yo autorizar y me cobran la tarifa más alta que no es de estudiante, aun no lo he pagado y por eso no puedo utilizar las herramientas. Cómo hago para solicitar el cambio de plan premium a plan standar y que me cancelen esa facturación ? No he logrado comunicarme con un agente, siempre dice que estoy en el horario que no atienden, Mil gracias, espero me puedan ayudar. 

We have a production issue this morning and a current outage of certain characters not rendering when getting the document back from the Adobe PDF Generation API. The image looks like characters are missing, but if you copy and paste, they are all there (ANNUAL PERCENTAGE RATE). It seems like you are not rendering the characters on your side (Font issue maybe). We haven’t made any changes to the templates being sent in, this is happening for any word document we send in to convert to a PDF. Again, some of these templates we have used for years with no problem up until today. This is urgent, please help! This is happening even after you marked the major issue for today as resolved: Adobe System Status

Hello, We have been using Acrobat PDF services, especially OCR PDF and PDF to DOCX on free tier, our usage have been increasing and we urgently need to get on paid subscription.I have reached out to sales multiple times via filling the form below, however there is absolutely no respnse.https://developer.adobe.com/document-services/pricing/contact/sales/ Would really really appreciate some help here.

As few (many?) of us have experienced, my inquiry to the sales service has never got any response so far.My company needs a higher monthly document transactions volume than what the free tier plan includes. Thus, I sent a quote request through the Contact Sales form on 27 March (email address: adobe@menant-benjamin.fr).Could someone at Adobe could kindly come back to us?Thank you,Benjamin.

While using the PDF Embed API, we found that some APIs have been deprecated by your company, which caused certain features we implemented based on the deprecated APIs to stop working. So I’d like to know: can we use a specific version of the API, so that our project won’t be impacted by your upgrades?One more question: if we use the One more question: if we use the “Push to production” feature, can it resolve the issue we’re facing? 

I used Claude.AI to troubleshoot, here is the feedback:Adobe Extract PDF API is silently dropping pages from this 94-page PDF. The text is fine. There's no difference in text format or layout between the missed and found contracts — pdftotext extracts them identically. So the common thread isn't about the content, it's about which pages Adobe Extract chose to skip. — pdftotext extracts every contract perfectly. Adobe just doesn't return text elements for certain pages, so the workflow never sees those Contract IDs.The input PDF has 94 pages with 52 unique contracts All 20 missing contracts have Contract ID: NNNNNNN in identical format to the 32 that succeeded — there's no text/regex issue Every page has a footer: Affidavit: Page X of Y (that's the numbering you mentioned) 18 of 20 missing contracts are single-page (Page 1 of 1) Pages 1-6 are ALL missing — the first 6 contracts were entirely skipped The remaining missing contracts are scattered (pages 21, 29, 48-55, 74-75, 77, 84, 94)

Hi, Have not been contacted by sales even though a week has passed. Is there anyone from Adobe that can help me to accelerate this?  Kind regards,Abyl

When the view div width is small, the search bar does not fully show. To reproduce this following code can be used<div style="width:35%"><div id="adobe-dc-view"></div></div><script src="https://acrobatservices.adobe.com/view-sdk/viewer.js"></script><script type="text/javascript">// Store the UI options in a constantconst previewConfig = { embedMode: "FULL_WINDOW", showDownloadPDF: false, showZoomControl: false}document.addEventListener("adobe_dc_view_sdk.ready", function () { var adobeDCView = new AdobeDC.View({clientId: "<YOUR_CLIENT_ID>", divId: "adobe-dc-view"}); // Consume previewConfig here. . . adobeDCView.previewFile({ content:{location: {url: "https://acrobatservices.adobe.com/view-sdk-demo/PDFs/Bodea Brochure.pdf"}}, metaData:{fileName: "Bodea Brochure.pdf"} }, previewConfig);});Notice the parent div of adobe-dc-view has 35% width. Now when the pdf is rendered, if we try to open search bar, the search bar

Today, we’re trying the PDF Services API. Strictly following the [Node.js SDK documentation](https://developer.adobe.com/document-services/docs/overview/pdf-services-api/gettingstarted/#nodejs), I signed up and created new credentials with the Personalized Code Sample Download, unzipped, installed the project dependencies with `npm install` and exported environment variables with client id and secret.Then, I tried to run a few samples... but every attempt (tried different operation endpoint) has failed so far:```$ node src/pdfaccessibilitychecker/pdf-accessibility-checker.js Logging configuration found at config/pdfservices-sdk-log4js-config.json.2026-03-27T16:13:47.606:[INFO]: Started uploading asset2026-03-27T16:13:49.060:[INFO]: Finished uploading asset2026-03-27T16:13:49.062:[INFO]: Started submitting PDF Accessibility Checker Operation job2026-03-27T16:13:49.063:[INFO]: Finished submitting PDF Accessibility Checker Operation jobException encountered while executing operation Servi

I need your help on pdfI have given a condition to the field in pdf which is when a user enters less than 6 digits, it should show the pop up notification and is written in java script and i wrote on custom validation script.But what i want now is when a user enter less than six digits and the field have any number, it should not allow the user to move to the next field, it should allow the user to go to the other cell only when he enter 6 digitswhat is happening in my pdf is when a user enter less than 6 digits it is showing the pop up notification, and not keeping the digits entered in pdf, and allowing to move to the next field so please help me on this

Hello,I am using the Document Generation API with a Word template, and I’m encountering unexpected behavior when using conditional-section inside a repeating-section.The Template tags I am using in word doc:{% repeating-section data.group_family.products %} {% conditional-section expr(id = "soft_bundles") %} Table 1 {% end-section %} {% conditional-section expr(id != "soft_bundles") %} Table 2 {% end-section %}{% end-section %}Sample JSON:{ "data": { "group_family": { "products": [ { "name": "Soft Bundles", "id": "soft_bundles" }, { "name": "Product A", "id": "prod_a" }, { "name": "Product B", "id": "prod_b" }, { "name": "Product C", "id": "prod_c" }, { "name": "Product D", "id": "prod_d" }, { "name": "Product E", "id": "prod_e" } ] } }}QuestionsIs there a known limitation or special handling required for inequality (!=) or negation (not()) inside conditional-section when used within a repeating-section? In e

I am using the Document Generation API with a Word template (dynamic table with table markers) and want to conditionally discard a column based on values coming from different levels of the input JSON.I want to remove a column when either of the following conditions is true:The current row’s product name equals a specific value (row-level context), OR A root-level boolean flag show_pricing is false { "data": { "approved_quote": true, "bypass_approval": false, "group_family": { "products": [ { "name": "Product A", "items": [ { "end_date": "31 Dec 2025", "prices": [{ "net_price": "$100" }] } ] }, { "name": "Some Other Product", "items": [ { "end_date": "15 Jan 2026", "prices": [{ "net_price": "$200" }] } ] } ] } }, "show_pricing": false} Template fragments I tried:{{items.end_date:discard

We have been using the PDF Services API to convert MS Office files into PDFs for over a year. We subscribed through AWS Marketplace, and the service has been working without any issues.However, we’ve noticed that we have not been billed at all during this time, even though in some months we have made more than 500 API calls. This seems unusual, so we’re wondering if there might be any issue with billing or with the data integration between the service and AWS.Could someone from the Adobe team check if everything is configured correctly on their side?

Using the pdfservices-sdk-samples for Java.Added the credentials to environment.Not able to connect to Adobe API, issue appears to be about SSL certificate.This was definitely not mentioned in the Get Started Guide.Exception encountered while executing operation: com.adobe.pdfservices.operation.exception.SDKException: Request could not be completed. Possible cause attached!com.adobe.pdfservices.operation.exception.SDKException: Request could not be completed. Possible cause attached! at com.adobe.pdfservices.operation.internal.http.HttpClientWrapper.executeApacheHttpRequest(HttpClientWrapper.java:159) at com.adobe.pdfservices.operation.internal.http.HttpClientWrapper.executeRequest(HttpClientWrapper.java:142) at com.adobe.pdfservices.operation.internal.http.HttpClientWrapper.lambda$send$0(HttpClientWrapper.java:113) at net.jodah.failsafe.Functions.lambda$get$0(Functions.java:48) at net.jodah.failsafe.RetryPolicyExecutor.lambda$supply$0(RetryPolicyExecutor.java:66) at net.jodah.failsafe

Hi All,We started getting the following error recently:DataCloneError: Failed to execute 'postMessage' on 'Window': #<Promise> could not be cloned.when calling the getPDFMetadata() method.Here’s the code:previewFilePromise.then((adobeViewer) => { adobeViewer.getAPIs().then((apis) => { // All viewer APIs can be invoked here apis.getPDFMetadata().then((result) => { numPages = result.numPages; pdfTitle = result.pdfTitle; }); .catch((error) => console.log(error)); }); });The pdf displays correctly in the viewer however the getMetadata() method fails and we can’t get the number of pages, … Is anyone having this issue?

Hi everyone,Since the 09/03/2026 update, the Adobe PDF Embed API has been failing to render PDFs that contain annotations. This was working perfectly before the update.Environment:- PDF Embed API (dc-core 4.7.7, dcpreviewdropin 4.2.0_2.1400.0, dc-comments-dropin 4.13.0_2.1414.0)- Issue occurs across browsers (tested Chrome and Firefox)- Only affects PDFs with annotations; PDFs without annotations load fineWhat happens:The PDF begins to load and is briefly visible, then disappears almost immediately. The viewer container remains but the document content is gone.Console error:TypeError: can't access property "icon", r[I] is undefined    QuickToolItem https://documentcloud.adobe.com/dcpreviewdropin/4.2.0_2.1400.0/bootstrap.js:2The full stack trace shows the error originates in QuickToolItem within the preview dropin, triggered during the commenting/annotation initialization flow:1. The PDF starts rendering via _startRenderingPDF → _preloadPageAtLowRes2. The comments dropin initializes via

Sehr geehrte Damen und Herren,ich habe versehentlich ein Adobe-Abonnement im Rahmen einer Testphase abgeschlossen. Dieses habe ich fristgerecht gekündigt, jedoch scheint die Kündigung nicht wirksam geworden zu sein.In meiner Nutzungshistorie können Sie nachvollziehen, dass ich das Programm bzw. die App nach Abschluss des Abonnements nicht verwendet habe.Ich ersuche Sie daher höflich, mein Abonnement umgehend zu kündigen und mir die bereits eingezahlten Abobeträge zurückzuerstatten.Für Ihre Unterstützung danke ich Ihnen im Voraus und bitte um eine schriftliche Bestätigung.Mit freundlichen GrüßenJey Mrlcvnmaral@gmail.com

Team,We are encountering issues with the PDF Services API when generating documents that include dynamic images.To assist with troubleshooting, we have attached a sample project and the corresponding request JSON object to this ticket.Steps to reproduce the issue: Run the application (built with .NET Core and Angular). Select the attached PDFTemplate using the ‘Select Template’ button Enter data into the loaded form (two text fields and one image field). Click the "Generate Document" button. Observed Result: The document is generated, but the images are not replaced; the output still displays the placeholder tags.Please help us in resolving this issue.Note: Sample project source code can be downloaded using this link https://drive.google.com/file/d/1VVJid-uq7102Yzw203OAdPHVqqjOlqED/view?usp=sharing

I’m facing a focus issue when viewing PDFs in Safari on macOS using the Adobe PDF Embed API Issue:When a PDF is opened in lightbox mode in Safari using Adobe PDF Embed API  Pressing Command (⌘) + F opens the search/find bar However, the cursor does not focus on the search input Typing immediately after ⌘F does nothing I must manually click inside the search box or press Tab to start typing