Acrobat Services API

I have a rather large document repository and many of the pdf documents sent to the embed API present a blank page. The document is fine in Reader and can be downloaded successfully from the embed API, but it's just not presented in the embed interface. Console logs errors about data corruption.http://docs.communityxs.com/index.cfm?id=10659

Document Generation - I'd like to be able to specify a datapoint in my json that may contain html for a list, is this possible or likely to be possible in the future?

Is there any way to get multiple text styles from a paragraph? Right now if a word or sentence in a paragraph is bold or italics, the adobe extract API considers the whole paragraph as bold or italics.(Sample files attached)

Used the PDF Extract API to extract info from PDF and build an HTML. Would be helpful if you can answer the following questions regarding the API: 1. Can you share details on how to identify the location of elements from the json output? "Bounds" key in the JSON seems to have info. But unsure if that's the right location info. 2. The documentation page here states that 'The output does not include headers or footers'. Is there any way this can be accessed? 3. The documentation page here mentions that 'headings that repeat across pages are reported for the first occurrence only.'. Does the structuredData include information about subsequent occurrences about the header? If not can you share details on how to identify different locations of the same header? 4. Text overlayed on an image (Test, $10M+ Rev) in this PDF (attached as PHT4) is extracted as a part of the image and not as text. The sections highlighted in the image are added as text. Anywa

Extremely Unclear Pricing for PDF Services, I want understand Adobe Acrobat Plan limits, like how many word templates can i fill in using your Power Automate connector. i'm not sure what it should cost after 6 months free trial (with only 1000 tokens which I will use in the first month), and I need this to communicate with my team so we determine if we want to move ahead with Adobe offering or not. initial volume will be about 1k a month. also it seems that there is a Acrobat Pro plan that enables you to work with cloud documents what are the limits on that plan? how many documents can i fill in per month?

Hello,I'm looking for web based pdf template builder and came accross adobe document generation api. I found that it have an Add-in for microsoft office to help build the template. My question if is there something similar to this add-in but can be embedded in a webpage. Thanks in advance.

Our viewer newly reports:index.js:1 Exception: t5::corrupt_data, The PDF is fetched through a URL. I can use the same URL to download the pdf and load it into Preview, Google Drive, Foxit viewer, etc. And I can see that there was recently a new release:  https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/releasenotes/#may-2023 Is there something we need to change on our side to get this working again?t5::corrupt_data at ___cxa_throw (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:28684) at self.___cxa_throw (https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.js:1:206) at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-function[676]:0x57969 at https://acrobatservices.adobe.com/dc-rendition-provider/3.0.2_5.4.0/AJS/wasm_acrobat.wasm:wasm-function[5024]:0x3c4462 at https://acrobatservices.adobe.com/dc-rendition-provider

Hi all. I just signed up to test/use PDF Services. The system set up my new dev account with some JWT credentials with big warnings that everything it just set up for me was instatly deprecated and should be migrated. Well, that's just Adobe (from my years of experience with them) I thought, and carried on. I tested a .net htmlToPdf doc generation (using the sample code in the .net SDK), which seemed to work - but then thought I should listen to the big red warnings and follow Adobe's advice about upgrading/migrating. The problem is, it now seems that there are no relevant samples, no documentation and no .net SDK support for using the API with the new pattern. Are all the .net SDK samples pointing to an old api that is deprecated? Did Adobe just point me towards a migration into a world where there is no support or documentation or any way of knowing how to use it yet? Hopefully I'm missing the obvious here.... but baffled.Adobe being Adobe again or just a daft use

Bit of an odd one this. I've tried several times to extact API pricing information from Adobe sales but receive nothing but silence back... and there's no pricing information available on any of the pricing pages either - regardless of what all the misleading links and copy suggest. We seem to have no choice but to invest our time in learning to use and improve the api with free trials - but without any way of knowing if it will even be a financial possibility to our clients. What's the buy in level? What are the mysterious pricing tiers that Adobe talk about? What are the minimum commitments? It's feels wierd to say out loud (and I hope I'm wrong) but the secrecy makes it feel like Adobe are acting in bad faith. How much time should developers invest in the service without knowing if it's even a financial viability for us and our clients? Are we being tricked? With rumours floating around of insanely high minimum commitments I'm worried that many of us are wasting our t

Hi,I used a dev account with trial only credentials to test the service.Once happy with it, I subscribed to the pay as you go service via AWS, deleted the project / credentials and created a new one (starting from the link in AWS), but I still get quota error, so it is not using the pay as you go paid subscription.Tried to contact support via the web form - no answer...I had to fallback to a second different trial account until this is fixed. How can I make sure I am using paid credentials ? Is there a way to double-check the credentials and licence I am actually using ?I tried many times to delete project / credentials and reissue new ones, but I always get the same error...

 Our viewer newly reports:index.js:1 Exception: t5::corrupt_data, The PDF is fetched through a URL. I can use the same URL to download the pdf and load it into Preview, Google Drive, Foxit viewer, etc. And I can see that there was recently a new release:  https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/releasenotes/#may-2023 Is there something we need to change on our side to get this working again? Thanks in advance

 I have a PDF with a dark grey-black blackground.  And I'm putting it on a website with an orange color background using the IN_LINE mode.  But there's a white-colored "gutter" that appears between the pages of my PDF.  Is there an option anwhere to either change the "gutter color" or remove the gutter completely?  Please advise; thank you!

We implemented Adobe PDF Embed Api around September of last year and we added our own UI outside of the viewer to be able to search the PDF using the provided search API.  We noticed this week that onResultsUpdate is no longer calling it's callback when a search term is provided.  We haven't found anything in the documentation suggesting that the search API has changed with any recent update, and we haven't changed our code.  Is this possibly broken or are we missing some change in the way the API works to get onResultsUpdate to fire its callback?

HiWe are developing a Public Sector web site, in the UK. This, like every Public Sector web site in the UK, is governed by Legal enforced requirements for Accessibility (WCAG 2.1 AA standard). This means that all text on the web site must be Accessible via a Screen Reader (e.g. NVDA - the most popular reader, and supported by Adobe).We tested the Embeded pdf capability of the Document Cloud View SDK (now called the pdf Embed api ?). It was great – just what we wanted – brilliant product. BUT – we then tested with NVDA.Failure – the Screen Reader cannot see the text based pdf – at all ! Export it to Standard Acrobat Reader, and NVDA ‘sees’ it fine. So there is a bug with the View SDK viewer.Retested using the Bodea test page athttps://documentcloud.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdfThis failed on NVDA – so its easy for Adobe support to check out. Made a Case - ADB-14021967-Y1N5 – you can see all the testing details there. Support asked me to p

I am trying to extract a pdf as individual images, and had the process working on Monday, but yesterday and today the endpoint is returning an error when polling for hte status of the job. Error is below. All other functionality is working (generating access token, requesting assetID, putting asset, executing job pdftoimages) - I've even verified that the pdf I'm placing as the asset is a valid pdf. Any insight into this error that may help?{"error": {#13165"code": "INTERNAL_SERVER_ERROR""message": "Unknown error performing transfer""status": 500}"status": "failed"}

I'm having issues trying to upload a local file using the presigned url. When I execute the `PUT` request I get an error SignatureDoesNotMatch - The request signature we calculated does not match the signature you provided. Check your key and signing method.Here's a snippet of my code.Note* I extracted the amz query strings from generated uri to make sense of the values being passed and the replace function was needed because I received a malformed error due to the encoded characters.export default async function uploadWordDoc( request: VercelRequest, response: VercelResponse ){ try { const {dlUri} = await uploadDoclink("docuExample") as DocResponse const {url, security_token, algorithm, date, headers, expires, creds, signature} = extract_amz_params(dlUri) const formData = new FormData() formData.append('file',createReadStream(join(__dirname,'..','/text.docx'))) const res = await axios.put(`${url}`,formData,{ headers: { 'Content-Type': "application/vnd.

Hey folks, I know some of you were concerned about recent emails about your credentials being deprecated. I've got a blog post on this that gives more details here:   https://blog.developer.adobe.com/important-update-for-developers-using-adobe-apis-bf25110d3b4?source=collection_home---7------0-----------------------   TLDR: If you are on SDK, just wait, we will be updating the SDKs soon, *MUCH* earlier than the end of support (Jan 1, 2025). If you are on REST, you *can* migrate now (my post shows an example). If you are on PowerAutomate, same as SDKs - sit tight.    p.s. None of this applies to PDF Embed.  

Viewing the example API page: https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf On chrome 96 available for windows at this link: https://chromium.cypress.io/win64/beta/96.0.4664.18 The API will not load instead go round and round. Our embedded devices use this version and we cant update them under any circumstances. Errors:Uncaught (in promise) RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): Wasm code generation disallowed by embedder). Build with -sASSERTIONS for more info.at abort (wasm_acrobat.js:1)at wasm_acrobat.js:1

Is there away to avoid http log post calls -https://dc-api.adobe.io/system/log.Is there any configuartion to turn this call off ?

Adobe Extract API fails to capture some of the images in pdf's when there are more than one page in pdf(Eg. Logo).When I try the same pdf by splitting into single page pdf, all images are getting exctracted.This is not just for one pdf, out of 100 cases with different type pdfs, 70% of multi page pdf's having similar issues.I tried with Power Automate Adobe API & Python SDK. Both showing same results.Anyone faced similar issues like this?

Is there a possibility to download PDF Adobe API via NPM ?instead dowloding it on run time usinghttps://acrobatservices.adobe.com/view-sdk/viewer.js"

Getting this error in the browser when trying to use PDF Embed API from a Wordpress site. Pretty sure I enabled CORS headers. Not sure who/what needs authorization. Can someone help? It would greatly appreciated! Thanks! Greg

Thanks for your kindness and support!  I need to update the PDF metadata property such as title, author, pdf producer, unfortunately I couldn’t find any API can update the metadata so far. I was wondering if you could provide me some guidence to find the correct API for this purpose?  From PDF properities API, I only be able to get the PDF properities, but I can't update the PDF properities. (https://developer.adobe.com/document-services/docs/apis/#tag/PDF-Properties)From Create PDF API, I'm not be able to insert PDF properities into the API. (https://developer.adobe.com/document-services/docs/apis/#tag/Create-PDF)  

Hi, I am using power automate connector to merge PDF and now that JWT account is starting to be deprecated - how can I setup the connector if it asks me for the private base key?   

Hi team, We are trying to use the adobe api for document generation, pdf services and signin. For the authentication purpose in the documentation it is mentioned like we need to upload a public key and certificate to the adobe I/O console. While I wasn't able to find the I/O console and add the integration as mentioned in the docs. But I tried another method like adding the I/O management or the I/O event service to my project and used the public key pair generated in that process. The API works fine when using that private key to generate the JWT and access token. Is this the current procedure or we need to use the open-ssl and generate a certificate and public key and upload them in the console? If so, please provide us with the details of where to upload the private key in the console. As far as we checked, when we add any API services, we get the service account authentication credentials and we don't see any such thing called the upload public key to the integration. Als