Acrobat Services API

Hi, I’ve been testing the PDF Services API (exportpdf operation) to convert PDFs into PowerPoint (PPTX), and I’ve run into an issue with fonts.In our PDFs, we’re using Roboto and Inter-Bold, and I’ve double-checked that they’re embedded in the PDF metadata. When I send the file through the API (tested with both the Node.js SDK pdfservices-node-sdk and the Python SDK, hitting pdf-services.adobe.io/operation/exportpdf), the output PPTX doesn’t keep those fonts. Instead, every text element defaults to Arial, and the spacing/layout looks off as well.I went through the API documentation and options but couldn’t find anything about controlling or overriding fonts. From what I can see, there aren’t any parameters exposed to handle this.Has anyone here run into the same problem? Is font preservation supported in PDF → PPTX conversions, or is it expected that custom fonts get replaced? Any guidance or workarounds would be super helpful — we need to preserve brand typography in client prese

to upgrade to paid credentials.; requestTrackingId=ef5bdb00-b107-11f1-8000-d2e5fa9da102; statusCode=429; errorCode=Quota Exceeded

[BUG] PDF Embed API (FULL_WINDOW): Page 1 renders blurry on iPad Chrome (CriOS) Mobile Site due to 1x mobile DPI overrideENVIRONMENT:- SDK: Adobe PDF Embed API / Acrobat Services DC View SDK (https://acrobatservices.adobe.com/view-sdk/viewer.js)- Embed Mode: FULL_WINDOW (defaultViewMode: FIT_WIDTH)- Device: iPad (iPadOS 16 / 17 / 18, high-DPI Retina screens with window.devicePixelRatio = 2)- Browser: Google Chrome for iOS (CriOS), specifically in "Request Mobile Website" modeDESCRIPTION OF THE ISSUE:When previewing PDFs in FULL_WINDOW mode on an iPad using Chrome's mobile website mode, Page 1 consistently renders blurry / at low resolution.1. On initial document load, Page 1 often flashes sharp for a brief split-second, then is immediately replaced by a fuzzy, low-resolution rasterization where fonts and vector lines degrade.2. Only Page 1 is affected. Scrolling down to Page 2, Page 3, and subsequent pages renders them crisply at native Retina resolution.3. Pinch-zooming in/out or scro

I currently have a collection of engineering technical standards in PDF format. After processing with the Acrobat Services API, the error rate for tables and figures is relatively high. In addition, the generated JSON‑formatted technical documents are overly large and contain excessive invalid information. How can I purify the data?

The document generation endpoint has returned a 500 INTERNAL_SERVER_ERROR for the past 24 hours.Here is a requestTrackingId: `46ab24b6-a0ff-4233-80b9-1e0ffcd2a47d`I’m using the Node JS SDK 4.1.0. I also tried the API endpoint directly, and I got the same result (US or EU endpoint)

Receiving this error "Flow run failed. Alert: Your operation has been throttled.: Looks like your flow's operation is hitting an action limit designed to protect the connector service being called." (429) in a Power Automate Flow, which is using connection reference to Adobe to convert a word file to PDF.Throttling does not make any sense as I made sure there is just one API call at a time. This error came out of nowhere, since all worked fine before. Anyone experiencing the same? Thanks in advance!

I'm having an issue with PDF Services API for the past 2 hours, there is a massive delay in responses and sometimes I'm getting this error message:UPLOAD failed for  with error: Unable to upload file: {"error":{"code":"Forbidden","message":"Forbidden, due to lack of authorization or entitlements. This is a permanent condition; refreshing the authorization token will not change the result."}}

I am developing server to server app to export a pdf to Adobe and get text back after OCR run.I can get the OAuth token just fine according to Step1 in the API docs. When I try to get a presigned URI which is used to upload the PDF that I want to extract text frrom, I get HTTP Error 400. The “text” that is returned in the JSON data from the call to the server is some simple HTML that contains the following info “openresty”.  I am not sure I’m calling the correct url to get the presigned URI. I’m calling https://pdf-services-ue1.adobe.io/assets which is what the docs say. The “assets” endpoint is implied. Some examples in the help forums call https://pdf-services.adobe.io/assets   which is different.The examples say to put my client id in the header as X_API_Key. I thought the “X” stuff was depricated years ago. It’s even more mysterious after just using “Client_ID” to get the OAuth token to do the call that is failing. Any way, I’m developing (figuring out how this works) with a Deskto

Flows were running fine as of yesterday, now all actions not executing.  Not getting failures, just clocking.

Hello TeamWe need to  upgrade requests package to 2.33.0. As there is a compliance issue.We can see that the in your latest build the version updated is requests  = 2.32.3.Are there any plans to upgrade this version from your end.Thank you

I understand from discussions with other Adobe Services API users that this appears to be a recurring issue. Multiple individuals, including myself, have completed the sales enquiry form on several occasions and have waited in excess of 14 days without receiving any response.Our organisation urgently requires an increase to the current 50-document limit, ideally before 27 July 2026, as this is becoming a critical business requirement.At this stage, I am simply seeking a clear indication of the available pricing and usage tiers. For example, a straightforward breakdown showing the number of documents included within each tier and the associated cost would enable us to make an informed decision and proceed without further delay.I would appreciate it if someone could contact me as a matter of urgency with this information so that we can arrange the appropriate level of service before our deadline.Thank you, and I look forward to your prompt response.

Hello,We have been using the Adobe API to convert HTML to PDF for years, but in the past week we have noticed issues with fonts.The HTML we are sending to Adobe has a clear definitionfont-family: "Trebuchet MS", sans-serif;However, last week we suddenly observe the output PDF uses a Helvetica fontHave there been any changes recently that changed the HTML-TO-PDF behavior?We are using this library to generate the PDFs@adobe/pdfservices-node-sdk

We use Adobe Embed API for years and all was fine, untill today started getting the error: Connecting to 'https://documentservices.adobe.com/dcpreviewdropin/4.3.0_2.1537.0/private/printHelper_main.d5df691a.js.map' violates the following Content Security Policy directive: "default-src 'none'". The request has been blocked. Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback. The impact is that the download and printer options are gone.

Hi Adobe Team,We're currently experiencing several issues with the PDF Embed API.We're using both Lightbox Embed Mode and Sized Container Embed Mode. In addition to the issues already reported in other community posts, such as: Feature config can't be set Connecting to ...printHelper_main...js.map violates CSP we're also seeing another issue where the viewer is not rendering correctly across multiple embed modes, with UI controls missing. For example, in Sized Container Embed Mode, only the scrollbar is visible while the viewer controls and content are missing.Sized Container DemoThe viewers are also not displaying as shown in the Modern Viewer documentation:https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/modernviewerThis is affecting our production environment, and we'd really appreciate it if the team could investigate.Is there anything we can provide to help speed up the investigation and resolution?Thank you,Jenn

Hello,I am working on Microsoft ERP - Adobe Reader API Integration. I am struggling with passing MediaType in Request via programming.I have followed Adobe Reader API Documentation and passing MediaType as per given example. But I am getting error when Request is sent via programming. The same works when I send Request using PostMan extension in visual studio code.Snapshot 1 and 2 give information about Adobe Reader API Documentation.Snapshot 3 and 4 give information about programming to send request and error that I am getting.Snapshot 5 and 6 give information about sending request from PostMan and its response.Any help or suggestion is appreciated.Adobe Reader API Documentation  Request and Response from Visual Studio code programmingRequest and Response using Postman extension in Visual Studio Code.

Hi,I’m using adobe generation for work (we have a subscription).I have a word template that I’m using to generate documents?I have here a template where I have a repeating section, and I would like inside that repeating section, to have a condition_section..But right now, the conditional-section is just ignored and it displays all the items inside the repating section.Can you help with that ?Thank you Here the exemple :  {% repeating-section parties.other_roles %}{% conditional-section expr($.role = "co-tenant") %}Sowie{{salutation}} {{first_name}} {{last_name}},geboren am {{birth_date_de}}{{address_line}},{{address_zip}} {{address_city}}{% end-section %}{% end-section %}

Submitted pricing request a few weeks ago, have not heard back. I see in the forum here that it’s a somewhat common occurrence. I noticed a reseller has offered to help - have any of you successfully worked with them (and if so, how does pricing look vs. Adobe direct)?

Hello, we hit our free tier quote, but I do not see a way to upgrade via the admin dashboard. I submitted a ticket but the 3 day wait time will be too long. Is there any way to expedite this process -  a phone number I can call or a way to speak to someone directly about setting up a paid account? Even better, any way to do this through the dashboard myself?

I see this morning that Document Cloud was having performance issues this morning. I have been trying to use the pdftomarkdown REST service api and the jobs have been stuck in progress since this morning. Document cloud has reported that the issues have been resolved, but any pdftomarkdown calls are stuck as In Progress when polling the status of the pdftomarkdown job 

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?