Acrobat Services API

1. Issue: Line segments jump unexpectedly when using the eraser toolSteps to reproduce:Click the line tool buttonClick the eraser toolLeft-click at the location marked by the red rectangleAfter clicking the left mouse button, an unexpected line segment appears adjacent to the red line 2. Are there any plans to incorporate line drawing functionality into the PDF Embed API?    

Hi everyone, We're excited to announce a new Adobe Community experience is coming this January. A little bit about the update:The new experience will be simpler to navigate, make it easier to connect with other creatives and Adobe experts, and will give you clearer ways to share feature ideas, enhancement requests, and bug reports—with greater visibility into their status with our product teams. In the meantime: Adobe Community will remain active. Keep using it as usual—there will be no interruption in access. In fact, you’ll notice even more Adobe Experts on deck to provide faster responses before, during, and after the update. No existing content will be lost in the update. Every single post, reply, solution, feature request, and bug report you’ve made will be transferred to the new experience. You won't need to recreate anything. Existing content will reappear in two phases. When we launch the new community, all posts created on or before November 16 will be there from day one. Aft

There appears to be an error in the source code for the pdf embed API. Even on the view sdk demo you can see in the console lots of errors:  https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf Uncaught (in promise) Error: No callback registered by viewer for GET_FEATURE_FLAG:  (yes, this is a repeat of an earlier post in the hopes that someone at Adobe will notice) https://community.adobe.com/t5/acrobat-services-api-discussions/repeated-error-in-console-in-relation-to-registering-callbacks-for-get-feature-flag/m-p/15605774#M10178

Hi, I'm using the nodejs code sample and attempting to use the Accessibility Tag endpoint. I'm getting this error:Exception encountered while executing operation ServiceUsageError: Either quota for this operation is not available or Free Tier quota is exhausted. Please visit (www.adobe.com/go/pdftoolsapi_home) to start using Free Tier quota or (www.adobe.com/go/pdftoolsapi_err_quota) to upgrade to paid credentials.When I go to the paid credentials link, it sends me to a web form to inquire about paid services. I've sent my information off, but this appears to be a black hole. Does anyone know if this is a legit api service or more of a POC? If it's legit, how can I pay for it?

Hello ,I am trying to get in touch with the Adobe Sales team regarding Enterprise Pricing for the Adobe PDF Services API (Acrobat Services API).I submitted the official Sales Inquiry Form more than a month ago, but I still haven’t received any response. This delay is making it difficult to move forward with planned work that depends on the API. Can someone guide me on how to reach the correct team or escalate this?Thank you.

i have xfa form those are created for IRCC canada https://www.canada.ca/content/dam/ircc/documents/pdf/english/kits/forms/imm0008/01-03-2025/imm0008e.pdftrying to import data in it using api but its not working tried differnt methods, can some help me to achieve it

We're a new company building a document accessibility solution that will use Adobe's PDF Services API and Auto-Tagging API to automatically make PDFs accessible and compliant with accessibility standards. Despite multiple submissions through the official contact form at https://developer.adobe.com/document-services/pricing/contact/sales/ over the past few weeks, we haven't received any response regarding enterprise pricing or volume discounts. Could anyone from the Adobe team provide alternative contact methods for API business development discussions, or share guidance on enterprise licensing requirements for these services? We're ready to move forward but need pricing clarity to finalize our technical architecture and business planning.

 Hello everyone, When I use "showAnnotationTools:true" all anotations from all users show up very nicely with the comments as in the first screenshot. Once annotations are finalised I display the same PDF as read-only with "showAnnotationTools:false" and then all details of existing saved annotations become invisible in the PDF enbed API (second screenshot).   So my questions are:Is there a way to display the PDF like the "showAnnotationTools:true" version but keeping it read-only / display-only where the users cannot add any new annotation or cannot edit any existing ones but can see the whole history? (this is the important part)Is it possible to directly open the right hand commenting panel by default when showAnnotationTools is enabled (like in the first screenshot) without the end user clicking on the "comments" button on the top right? Also, if my first request (opening read-only with annotaions/comments showing) is not currently possible,

I am doing some testing with Adobe PDF services APIs and everything seems to be working, but I get an error that says "Job completed but no downloadUri found" and when I look into .\last-status.json I see an error that says "AccessDenied" "No AWSAccessKey was presented".  I am using the code on the Adobe site with the tokens and keys provided on the Adobe Developer Console.  I'm not sure what I am doing wrong. If anyone could help me out that would be great. 

Olá, preciso aumantar a capacidade de chamadas no PDF Services API, estou tentando mas esat complicado, alguem tem alguma dica?

Hi Adobe Community.I can't make PDF Services API work. Here is what I do.curl --location 'https://pdf-services.adobe.io/token' --header 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'client_id={{Placeholder for Client ID}}' --data-urlencode 'client_secret={{Placeholder for Client Secret}}'Response:{"access_token":"{{access_token}}","token_type":"bearer","expires_in":86399}curl -L -X POST 'https://pdf-services.adobe.io/assets' -H 'X-API-Key: cef2562e3499476c8d8543291a16f8f1' -H 'Authorization: Bearer {{Placeholder for access_token}}' -H 'Content-Type: application/json' -d '{"mediaType": "application/pdf"}'Response:{"uploadUri":"{{uploadUri}}?X-Amz-Security-Token={{Security-Token}}&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20250524T071921Z&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Expires=3600&X-Amz-Credential={{Credential}}&X-Amz-Signature={{Signature}}","assetID":"urn:aaid:AS:UE1:ad2257b2-5xxx-4f7b-xxxx-377xxxxxa08b"}curl -L -g -X PUT

Hi Team, I am using the Document Generation Word add-in. I have inserted a page break in the Word document, and we also have a few conditional sections. However, when generating a PDF using the tool, the content is shifting upward. Does the tool recognize page breaks? If yes, why is the content moving to the previous page, and how can this be handled?

Hello, Would like to download the pdf file from Adobe Acrobat   using any of the programming language. I have read all the documentation through this link and nothing helps --> https://developer.adobe.com/document-services/docs/overview/pdf-services-api/ Thanks in advance  

Is it possible for delete events in the SDK to be triggered without direct user action? One of our users reported that their annotations were deleted even though they didn’t initiate any deletion themselves. I’m trying to understand whether this is something the SDK could trigger automatically under certain conditions. Any insights would be appreciated!

Can I get a report of my plug-in downloads from the Creative Cloud by counts by region, by version, or by user type (free vs paid)?

Hello everyone!I'm trying to load a PDF with layers, and although it loads easily, I can't find a way to activate and deactivate layers to view it interactively. Do you know what I might have missed?

Currently, the PDF Embed viewer supports text annotations, highlights, and freehand drawing, but it does not provide simple tools for drawing standard geometric shapes such as rectangles or circles. For many use cases — including document review, form markup, architectural sketches, and technical diagrams — users need to add clearly defined shapes rather than hand-drawn lines. While it’s technically possible to simulate shapes using custom code and the AnnotationManager, this approach is not user-friendly and tends to produce inconsistent or distorted results. A native, integrated solution within the Embed UI would greatly improve usability and align with the experience in Adobe Acrobat. 

Hope all is well. I've reached out to sales mulitple times in the past couple of days but have heard nothing back. What is the pricing for Document Services API after the 500 limit?Thanks

I saw a similar post recently. We're a startup building and testing the MVP - part of the workflow involves parsing PDF documents. We tested with Adobe's services - but quickly consumed the 500 free credits....we're interested in figuring out the pricing and terms of continuous use.Despite multiple submissions through the official contact form at https://developer.adobe.com/document-services/pricing/contact/sales/ over the past week, we haven't received any response regarding enterprise pricing or volume discounts. Can someone from the Adobe team please reach out / ping me with a private message so I can share my account information, to get this moving? We have a narrow window of a few days where we need to lock down a service  - my preference is Adobe - if you can respond soon!Many thanks.Raman

There appears to be an error in the source code for the pdf embed API. Even on the view sdk demo you can see in the console lots of errors:  https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf Uncaught (in promise) Error: No callback registered by viewer for GET_FEATURE_FLAG:It then logs errors for the different options.

Hello -So I've disabled printing and downloading in the embed API per the documentation (showPrintPDF and showDownloadPDF are set to false). I've also set a css attribute to @media print { display: none} for the container div. Both of these methods work and cover the file -> print (PDF does not display in file -> print which is good). However, when a user mouses over the document and hit CTRL (CMD) + P, they are still able to print. How can this be disabled? I've tried the @media print route with no luck. Screenshot attached of the print dialog that comes up with CTRL + P.

when I use the embed API, the Download button is only visible after clicking the `...` button in the top-right corner.I’d like to make the Download button visible directly (outside the menu).Is there any way to control this part of the UI?  

Hi,I have been trying to reach Adobe Acrobat Services API Sales team via the online form a couple times . Once submitted, I get the message that they will contact me in a few business days but I never received any call or email back from them.Has anyone faced this issue  and was able to resolve it ?Many thanks.

I would like to be able to use the Acrobat Services API to convert Word documents (and other formats too) to archival compliant PDFA documents. It is not clear if the createpdf REST api endpoint supports PDFA format. There doesn't seem to be a way of specifying the output format. I would like to be able to create compliant documents and also have a way of verifying that the document is compliant either by using another REST api endpoint or by receiving a certification report in the json response from the createpdf endpoint. Does anyone know if this is possible or in the pipeline for future development?

Hi everyone,I'm currently integrating Adobe PDF Services REST API (without SDK) in a Node.js server.Everything works fine until the final conversion step.Here’s my full sequence:1)Token (IMS)POST https://ims-na1.adobelogin.com/ims/token/v3→ Works, I get a valid access token.2) Asset Upload (HTML or ZIP)POST https://pdf-services.adobe.io/assets→ Works, returns a valid assetID (e.g., urn:aaid:AS:UE1:xxxx).3) Conversion to PDFPOST https://pdf-services.adobe.io/operation/createpdfHeaders: { "Authorization": "Bearer [token]", "x-api-key": "[client_id]", "Content-Type": "application/json" }  Body (latest attempt): { "intent": "createpdf", "inputs": [ { "assets": [ { "assetID": "urn:aaid:AS:UE1:xxxx", "type": "application/vnd.adobe.asset+zip" } ], "type": "application/vnd.adobe.input+zip", "params": { "pageLayout": { "size": "A4", "orientation": "portrait" }, "includeHeaderFooter": false } } ], "outputs": [{ "type": "application/pdf" }] } → ❌ Always returns: {