Acrobat Services API

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

All,We wanted to explore an option to use Acrobat Services API. Upon further analyzing the process, it looks like it actually uploads any DOCX to Acrobat Cloud Server to do the conversion.Our requirement does not allow us to upload file outside of our organization becuase of PII/PHI. Is there any software (DOCX to PDF) that we can install on our servers and make an API call to that software on our servers?

Hi, I'm struggling to figure out how to sign up fpr Adobe PDF services.  A couple of weeks ago I signed u for the trial, received credentials and sample projects and started using the service. Now I need a paid account so we could continue using these services.My company's sys admin was directed to sign up through AWS and we found the service subscription there but how can I get the credentials from that subscription?

Hi, the bounding box for text comments behaves a little odd, if the displayed page is rotated 90 degrees. The boundingbox itself is rendered correctly, but the text gets cut off or line breaks are inserted at the wrong places. It seems like the width and height of the bounding box are swapped.

I want to get all the extracted images using Extract java sdk as byte arrays instead of the zip file. 

For the attached, document ween we send to the API endpoint we recieve a JSON that references figures as full page images instead of the text. We tried converting to postscript and back to PDF to no avail. I find it interesting that even if the document is OCRd, we still run into this problem. Is there any advice on how to handle this?

Got some attributes in a response object that appear to be undocumented. I have a 100 page PDF and the majority of pages have their text extracted. The one in question though is instead extracted as an image. The JSON in question look like: { "Bounds": [ 79.85000610351563, 108.1837158203125, 546.1023712158203, 714.25 ], "Page": 80, "Path": "//Document/Figure[3]", "attributes": { "BBox": [ 80.03669999999693, 108.38799999999901, 530.0179999999818, 714.002999999997 ], "Placement": "Block", "Suspicion": "{ \"suspicious\" : true, \"reason\" : \"complexTable\" }", "SuspicionFBName": "region-complexTable", "Suspicious": true }, "filePaths": [ "figures/fileoutpart18.png" ] }Can anyone help me understand what the "Suspicion", "SuspicionFBName", and "Suspicious" attributes mean? The data is formatted in a rough table for this section, but the table spans several pages and this is the only one to b

I signed up for a Document Generation trial - it's been great. I've spent months learning Adobe Document Generation API and developing a system to make use of it.However, now that I'm ready to subscribe, it seems that's not possible.I've sent multiple messages via the Adobe Sales Contact Us forms, but heard nothing in reply.I now learn that, for some reason, there are multiple posts in this forum suggesting this API is unavailable in Australia.Adobe, some help please:Can somebody please clarify the situation?If the API is not available, why wouldn't Adobe (and any developer) regard this as an unacceptable and misleading situation? It's clear from my account details that I'm in Australia and using an Australian email address. Surely offering and providing a trial account to a person carries some implicit assurance that the service is available to them?If truely not available, this seems a significant risk for many Adobe developers and projects. And how do we recoup our time an

Trying to integrate this with my Ionic Capacitor iOS app, and receiving the following error "This application domain (capacitor://localhost) is not authorized to use the provided PDF Embed API Client ID." - When running ionic through my browser (localhost:8100) it displays the PDF file perfect, but when testing on an iOS device I am seeing the File preview not available error. My client ID domain is setup as localhost, but i cannot set the domain to capacitor://localhost - Any suggestions?