• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

What is the difference between PDF Services API and the Acrobat Sign API?

New Here ,
Jan 31, 2023 Jan 31, 2023

Copy link to clipboard

Copied

We would like to use the PDF Services APIs to manipulate and extract PDF data through a web application. I understand the only way to trial the APIs is to use a personal Adobe account, and the pay-as-you-go requires purchasing from the AWS Marketplace.

I spoke with my Adobe account rep who seems to be pushing us toward Acrobat Sign. I understand the Acrobat Sign API works complimentary with the PDF Services, but it appears to be its own thing and requires a separate Developer Account. I'm assuming the PDF Services APIs are not included with the Sign API and I can't tell if  its free to use or also pay-as-you-go. I don't think we would use the Sign API anyway.

As the admin of our Adobe account, is there anything I need to do through our Admin Console to provide access to the APIs, or is this completely separate from our other CC and Acrobat licensing? 

Thanks!

 

Views

194

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jan 31, 2023 Jan 31, 2023

Copy link to clipboard

Copied

Almost all of that is incorrect.

The Acrobat Sign API is available to Acrobat Sign users with an Acrobat Sign Solutions class license (Enterprise). If you are using the SaleForce integration, the integration includes Document Builder which is an implementation of the PDF Services API Document Generation service and the cost is built into the Sign transaction but this is the only part of Acrobat Services API that is included and you don't need a separate account for use with the Sign integration. You don't need a developer account to access the Adobe Sign API.

 

All of the services under Acrobat Services API do require a free developer account. Creating the account is free because we have free tools. For services that we charge for, transactions can be purchased through AWS for pay-as-you-go or through an ETLA through your account rep. If you go through AWS, you manage the credentials through AWS. If you go through an ETLA, you manage the "users" through the admin console and the credentials through the developer console. I put users in quotes because you can have one user with multiple credentials that are used by different departments for the various solutions that you might be building. How you manage the "users" is up to you depending on how you want to manage chargebacks if that's a requirement.

 

I'm not sure why your account rep would be pushing you toward Acrobat Sign. You'd need the Extract API to extract information from a PDF and Acrobat Sign API doesn't do that.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 02, 2023 Feb 02, 2023

Copy link to clipboard

Copied

LATEST

@AttainmentCraig  can you please send me an email at amohssen@adobe.com

I'd like to understand the situation better and make sure we can make sure this doesn't happen again in the future - thanks.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources