Skip to main content
New Participant
June 4, 2020
Question

How to get the application client Id from integration key (access token)

  • June 4, 2020
  • 1 reply
  • 2436 views

Hi,

I am integrate Adobe Sign into our application which cannot use OAuth to get the AccessToken. I created the access Token via this link https://secure.eu1.echosign.com/account/accountSettingsPage#pageId::ACCESS_TOKENS

I created an API application in this link https://secure.eu1.echosign.com/account/accountSettingsPage#pageId::API_APPLICATIONS
Then in my application, I create an webhook via API using the access token above. the problem is the webhook is using different x-adobe-client-id which I am guessing it comes with the access token.
How can I get the client-id from the access token so I can verify the header from webhook URL? 

This topic has been closed for replies.

1 reply

atsmusz_as_dsEng
Adobe Employee
Adobe Employee
June 17, 2020

As described in our helpx page on web-hooks in the section "Verification of intent of the webhook URL" here, the "Client ID" related to any "application" making webhook calls out from Adobe Sign to a customer or partner's platform will have a "header parameter" called X-AdobeSign-ClientId.  This ID needs to be picked up from the incoming webhook and echoed back to Adobe to verify the "intent".  If the webhook was created through the Web-UI "front-end", the Client-ID will not match your oAuth application Client-ID.  This will only match if the web-hook was created via the webhook APIs while using an "access token" acquired for use in your integration with web-hook creation specific permissions.  For webhooks created in the Web-UI, this Client-ID will be a "general" one matching the "Adobe-Sign" application as a whole.

 

Aaron Smusz - Data Science Engineering - Adobe Acrobat Sign
New Participant
June 18, 2020

It seems that you misunderstand my question. How can we get the X-AdobeSign-ClientId from the "access token" created via Account > Personal Preferences > Access Token? (https://secure.eu1.echosign.com/account/accountSettingsPage#pageId::ACCESS_TOKENS)


atsmusz_as_dsEng
Adobe Employee
Adobe Employee
November 15, 2020

The x-adobeSign-clientId is in all the "headers" we send to your webhook URL.  If you created the webhook via API using that token it should contain the "clientID" for your oAuth app.  However if you created the webhook from within your AdobeSign account through the web UI, the Client ID is the same for everyone because the app used is the Adobe Sign front-end.

Aaron Smusz - Data Science Engineering - Adobe Acrobat Sign