Does Adobe Sign still support Integration Key?

[Quang Tran The]

I'm currently trying to build a back-end system, i.e. no user interface which should send documents out for signature using Echosign.

The page for configuring the Oath token requires a redirect URL, but obviously my application doesn't have a UI and therefore no redirect URL either.

Clearly there is a whole OAuth world that I can dive into now, but I'm hoping to use their API quickly without needing to understand all the ins-and-outs of OAuth first. All of the samples seem to be based on a web interface scenario, which is not the case for me.

I have found another option is to use the Integration Key as Access Token. The last post is 3 years ago, then i am not sure Integration Key is available or not

[J_McNeece]

Hi @Quang Tran The ,

Are you refferring to the webhook URL required for creating a webhook in Sign? If so this is part of Adobe verification of intent to verify the webhook, more information can be found here Webhooks overview (adobe.com)

If you are looking to integrate with APIs there is no URL required. Review the APIs here REST API — Document e-signature Software — Acrobat Sign (echosign.com)

[Quang Tran The]

Hi @J_McNeece 

Thank you for reply.

I am going to use the Adobe Sign REST API (https://secure.na1.echosign.com/public/docs/restapi/v6) on my backend system. All APIs require the access token for authentication. On https://secure.na1.echosign.com/public/docs/restapi/v6, the access token is OAuth Access Token. I have found that there is an Integration Key, that could be used by legacy system (not support OAuth).

My question is Adobe Sign still support Integration Key or not.

[J_McNeece]

@Quang Tran The Rest API v6 works with access tokens created in the Adobe Sign UI. In the UI you will define the scope of you API call. Once completed that Bearer token will get you a successfull 200 response from resapi/v6