PDF Services API

[Konrad30517313ovh8]

Hi,

We have subscribed to the PDF Service API in AWS Market. We learned from a message on the AWS website that it will no longer be possible to subscribe to this service in AWS Market. Do any of you perhaps know how the redemption of this service will be done now or do I have to change something ?

Thank you for the information

[Raymond Camden]

Hi, reach out to sales here: https://developer.adobe.com/document-services/pricing/contact/sales/

Also note we have a free tier launching in a week. If you will use less than 500 transactions per month, you will be covered.

[Alan3055392546xe]

I signed up for a free trial last week and all was working until yesterday, now I'm receiving a message: description ='Access forbidden; transactionId=jGPaoxj0DmwN6RmMQBaBfCumgP7IbWQO'; requestTrackingId='IrtdRWI8p1D2hjX48D0dEtLvg17ncVdv'; statusCode=403; errorCode=FORBIDDEN

Does this have anything to do with the above change to the PDF Service API in AWS? Also, will the endpoint be re-enabled in a week or is something else going on? Thank you!

[Raymond Camden]

It should not. I don't suppose you still see the issue, do you?

[Alan3055392546xe]

Hi Raymond,

Still seeing the issue. Is the tracking id or transaction id useful? Here's the latest: description ='Access forbidden; transactionId=uQ3ShUbW2aI4SIqtNJRZkPSShQmw5k51'; requestTrackingId='c8iC5TTWdyjODR5koeCCFwHsRAKjvcKU'; statusCode=403; errorCode=FORBIDDEN

Should I create new credentials, or do you think this is a different problem? Thanks - Alan

[Raymond Camden]

Your credentials should not have been touched, but making new ones would be quick and easy way to check.

[Alan3055392546xe]

Hi Raymond,

I created new credentials but using them generates the same response (different transactionId and TrackingId). Is the original authentication method using pdfservices-api-credentials.json still supported? I see it's been deprecated but indicates that it's supported until January 2025. 

Thanks,

Alan

[Raymond Camden]

It should be - can you share the code you are using?

[AllTheViews]

Hi,

I finally got this working again in the new free tier mode. Our server had been working fine until it reached it's 1,000 document quota. On advice from Adobe,  I set up a new user account and created new credentials and the system worked fine for about a week and started generating the above response, this was before the new tier switch-over at Adobe. Now I have updated the project to reference the new SDK, version 3.4.0. The main code change is this (from Adobe's sample source):

--------------------------
// Initial setup, create credentials instance.
Credentials credentials = Credentials.servicePrincipalCredentialsBuilder()
.withClientId(System.getenv("PDF_SERVICES_CLIENT_ID"))
.withClientSecret(System.getenv("PDF_SERVICES_CLIENT_SECRET"))
.build();

------------------------

Note the call to servicePrincipalCredentialsBuilder is new from the prior SDK. You can set the credentials as enviroment variables but for some reason in my implementation that didn't work so hard-coding them in the call resolved that issue.