Questions

I’ve been using the pdftomarkdown REST api up until a few minutes ago where I am getting an error 500 INTERNAL_SERVER_ERROR when polling for the finished job. Same file I’ve been using that worked fine now returns the error 500.Request Id from response header: M1ttO6fDeXuIuwpfDdi90Ha0xOePVOsw

I need to work Adobe api for my Salesforce org.I already have some predefined PDF templates (PDF_TEMPLATE). Our goal is not to generate these PDF templates using the Adobe API.Instead, we want to:- Use the existing PDF templates.- Populate the PDF form fields with data from Salesforce.- Use the Adobe PDF Services API only to fill or extend the existing PDF template. We already have PDF templates, and after filling them with Salesforce data, the output must look exactly the same as the original PDF. These are sensitive business documents, so we cannot change or redesign them.In this case, do we need to convert the existing PDF templates to make them compatible with the Adobe PDF Services API?If yes, could you please guide me on how to do that while keeping the PDF layout exactly the same?Thank you!

I am going to use abobe api service for my Salesforce org.I have one more question about the Adobe PDF Services API.Can Adobe populate a dynamic table in a PDF?Let me explain the scenario:I have a PDF template where the table header and overall layout are fixed, but the number of data rows is dynamic.For example, Salesforce may return:- Sometimes 1 row- Sometimes 3 rows- Sometimes more than 10 rowsCan the Adobe API automatically add the required number of rows and populate the table with the Salesforce data?Also, at the end of the table, I may need to display calculated values such as:- Subtotal- Grand Total- Total QuantityIs this type of dynamic table generation supported by the Adobe PDF Services API, or do I need to use another approach or service to achieve this?

We are using Adobe PDF Services API to generate PDFs.Issue:PDF generation is failing with API response code 143.Request ID:5iYYHLGvyTasHEJxpGkTcvdUH7A3w82GWorkflow:1. User signs a form.2. User clicks Save.3. A background process calls Adobe PDF Services API.4. PDF generation fails and the API returns code 143.We were able to reproduce the issue in our DevOps environment.Adobe does not appear to return a detailed error message.Could someone from the Adobe team investigate the request ID and provide the underlying error details and recommended resolution?

Hola quisiera que por favor me ayuden con el  reembolso de mi dinero ya que por error realize la suscripción y fue mas que nada porque decia 7 dias de prueba gratuita lo cual no fue asi y no la necesito me dijeron que si realizo la solicitud de reembolso dentro de los 14 dias me pueden reembolsar el dinero 

We are using Adobe PDF Embed API to display and edit PDF forms containing AcroForm fields.Some of the PDF fields are already populated by a third-party clinic before the document is loaded into our application. These prefilled values display correctly when the PDF is initially opened.However, when a user clicks into one of these prefilled fields and edits the value, the text rendering becomes incorrect. The updated text appears clipped, partially hidden, or misaligned within the field boundaries.Expected BehaviorWhen a user edits a prefilled form field, the text should remain fully visible and properly positioned inside the field.Actual BehaviorAfter editing certain prefilled fields:Text becomes partially hidden or clipped. Text appears misaligned within the field area. The original prefilled value displays correctly before editing. The issue occurs only after the field is modified through Adobe PDF Embed API.Steps to ReproduceOpen the attached PDF using Adobe PDF Embed API. Navigate t

For certain sets of documents, I’ve been encountering a GatewayTimeout error during the merge process.The previous steps, where the documents are collected into an array, complete successfully. However, the merging step consistently fails with the GatewayTimeout error.We are subscribed to the 75k document transaction pack, and we expect this process to run smoothly without disrupting our daily operations.

Hello Community and Adobe Support Team,I am currently using the Adobe PDF Services API (specifically the "Extract PDF" operation) in my application and am receiving a QUOTA_EXCEEDED error. My current monthly quota of 50 transactions has been exhausted.This API functionality is business-critical for our application, as it is essential for extracting images from PDF documents for our customer processes. Since the quota was exceeded, we are no longer able to offer these vital functions, which leads to significant operational limitations.Due to the sharply increasing needs of my users, it is urgently necessary to significantly increase the monthly quota for this API as soon as possible.Could you please immediately inform me of the steps I need to take to request a fast quota increase for the "Extract PDF" operation of the Adobe PDF Services API? Are there specific contact forms or processes for such urgent requests?We depend on a timely solution to be able to fully offer our services again

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