API Applications with multiple Adobe Sign instances

Question

Hello,I have issues integrating the adobe sign api into my companies application. I am new to acrobat and adobe sign so I do not understand the core infrastucture of the service and how adobe sign instances are separated. My main question at the moment is this:Where do I have to create an API Application?Implementing the adobe sign api was requested by one of our customers which has his own adobe sign instance (e.g. https://customer-dev.eu1.adobesign.com) but we are working on a solution that works for all customers including new ones in the future. Do my customers have to create their own api application and provide their client id and secret or does my company need an adobe account (e.g. on https://api.eu1.adobesign.com) and create the api application there once and than use it for all of our customers? Are these adobe sign instances strictly separate or can one instance use an api application of another instance?Thanks

atsmusz_as_dsEng · Accepted Answer

Hi @birk_8853 ,Re "my company is aiming to become an ISV partner." -- Great!    Re: "my company only needs to create one certified Partner API application" -- Yes. Typically you will create one for development, and perhaps another later that will become your "certified" partner app so you can make changes as needed during dev/testing, but these will both be able to be used by users in any account accross the Sign platform.  You will want to use a page on one of your servers that's publicly available for your redirect_uri as mentioned here.  This is the place where the oAuth exchange will happen that allows users in "external" accounts to get API tokens to allow them to make calls using your partner app.   Re: "I also have a few other unrelated questions about the Adobe Sign API." -- You can certainly post your questions here, or in more individual posts.  This is up to you. Please email me at smusz@adobe.com if you like, and I can connect you with the technical resource for ISV partners?

atsmusz_as_dsEng · Answer

Hi @birk_8853 .

In the case where developers represent what we typically refer to as a "partner" we generally have 2 different types.

OEM Embed - These are companies that have a platform they would like to integrate with Sign who want to set-up a relationship with Adobe where they actually purchase "transactions" in bulk and offer Adobe Acrobat Sign as the sole e-signature functionality for users on their platform.

ISV - These are companies that simply want to allow their platform-customers to get their own Sign account ( or in some cases the customer/s already have it ) directly from Adobe and use an integration for Acrobat Sign from Adobe. Some of these partners offer a few different integration options their customers can use for e-signature.

In both of the cases above, we have the ability for partners to create a "partner" scoped API app that lives typically in a developers account which can be used by any Adobe Acrobat Sign account with the ability to access the API.

So ... to answer what I might think is likely your next question, you should create a partner scoped oAuth app in a devleoper account and then you can test your "uncertified" partner app as outlined here:

https://opensource.adobe.com/acrobat-sign/embedpartner/partnercertification.html

Please let us know if this addresses your questions?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded