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

@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.

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.