Acrobat Services API

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?

Was this functionality removed in the Modern viewer? If so, why remove that option?I can no longer right-click to download documents from the viewer, and I know this functionality was working before. Currently the only way to download documents is through the three-dot menu icon on the upper right corner. We have some concern that users will overlook this menu and not be aware of the option to download. I think it would be ideal to have a download button or icon the top menu bar where it is more visible (with the ability to toggle on/off through the configuration options). It looks like there is a download button in the top menu bar only when annotation is enabled and when using the "FULL_WINDOW" embed mode. I am currently using the "LIGHT_BOX" embed mode so even this is not an option for me. Are there any workarounds for this to enable downloads outside of the three-dot menu? 

I received an email from adobe stating I "MUST transition over to the new modern PDF viewer within 10 days". Unfortunately, I am using the In-line embed mode, and in-line embed mode for the new PDF viewer does not work properly. In-line embed mode for PDF Embed API does not allow text to be highlighted, copied, or for links to clickable (even on Adobe's own example page):https://documentservices.adobe.com/view-sdk-demo/index.html#/view/SIZED_CONTAINER/Bodea%20Brochure.pdfTrying to select any text just results in a blue border around the pdf ... no text is able to be selected, and no links work.  I need this function to work (otherwise, the pdfs are just images) The legacy PDF viewer works properly in inline embed mode, which is why I am continuing to use it.The new PDF viewer used to work, but in december something changed, and this functionality was lost.  Every other embed mode (Full Window, Sized Container, Lightbox) still allows for

While generating access token using JWT for Document Services APIs, it is expiring within 24 Hours. Can someone please advise if we have a refresh token endpoint to refresh the expired access token, or do we need to generate the access token again after 24 hours?Thank you.

I used 'https://pdf-services-ew1.adobe.io/assets', and got following response:{ "uploadUri": "https://dcplatformstorageservice-prod-eu-west-1.s3-accelerate.amazonaws.com/16a9de6d208743239d1f694295f12626_254127B763EDC88B0A495FC7%40techacct.adobe.com/471bc6c7-d837-4817-891c-7d042b3025b6?X-Amz-Security-Token=FwoGZXIvYXdzEP%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaDIaZ0FfEsaBPTEBY9yLUATxRYzDjDFilQARDSnyOSy2XdBy%2FoL2cLd5OacEA%2FWLosaEJ75p%2BeOwO0ITohEt14Tw7gCamc7OBXD1CR3%2B4tt1%2BT3iM6FT5KwYoFlcyWN00WNg53eWaRrKAqeaZYAOYG6r6BNaZLSx9eMf4KX8audyoDX3ZLrvu9XSQtkBLAzlC5hab0C5voHrGXhwKo6jVMZV1Fea0KQZ7nACQ3woWJ6FdjEgPijk0RDwk3KjpLTnc9IU%2B%2F1AdmcaJ5ozJ0%2B8OUoiluWGS14OPMoD%2FeDlnBOCsSnuvKPD0xp8GMi01KKrkxRzzmVb0nXgyk2vE2dlkWoCk9XT%2FGkeIQdSVrU9QFLfLxtHgF4qeIvU%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20230219T061237Z&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Expires=3600&X-Amz-Credential=ASIAWD2N7EVPIZMO5LHX%2F20230219%2Feu-west-1%2Fs3%2Faws4_request&X-Amz-Signature

Trying to access variables 2-3 levels deep,  to be able to access variables that deep, do I need to flatten first?  Thanks in advance.

Im trying to extract table data using Adobe Extract API.For normal tables, the cell information is coming correctly. But when the rows contain different width columns, it fails to provide exact column count.Also, the main issue I have right now is, for empty columns, page no field is missing from the TD style element in JSON output.(Screen attached) 

Can this API or any other Power Automate service add a page in an existing PDF?I would like to have a PDF page (that has user's name, approval status and timestamp - all text) be added as an additional page in an existing PDF.