Service Account Integration with Adobe Sign

Report · Feb 05, 2021

Hi there,

I'm investigating whether my company's product can consider an integration with Adobe Sign. Our platform intends to use a single service account for all interaction with the API, because we can't assume that our end-users have Adobe Sign accounts. All agreements would be sent and managed by a single service account, and our end users should not need to perform any interaction or consent with Adobe at the point when our integration acts using said service account. Does your API offer support for this scenario? Looking through your documentation, it seems to assume that all end-users of any integration will need to have Adobe Sign accounts of their own, and will need to manually sign into those in order for the API to act on their behalf using standard OAuth. Other eSignature providers support this by allowing service integrations to authenticate via JWTs, and I notice that Adobe Developer Console supports that but Adobe Sign does not as far as I can tell. If you don't support it now, is there any plan to support that scenario in the future?

Thanks

Report · Apr 24, 2023

Did you ever get this figured out? I'm looking for this same solution.

Report · May 11, 2023

Although it's a non-trivial setup, there is a way to use technical accounts configured in Adobe Identity - IMS and their related tokens with Sign APIs.

https://helpx.adobe.com/sign/using/sign-technical-accounts.html