Copy link to clipboard
Copied
We have configured a web hook with Event "Agreement Action Completed" and selected "Include Signed Agreement" Notification parameters. However the attachment stream of signed agreement is not being sent as part of the response.
Also the Payload attributes doesnt mention anything about "Signed agreement" attributes.
https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/webhooks/webhook...
Can someone let us know how and when will "Include Signed Agreement" Notification parameter work.
Copy link to clipboard
Copied
it should include the signed pdf as base 64, though I advise against grabbing the signed pdf from the webhook and only use the this webhook event to make a call to
a few reason for this, one there's a non-zero change te signed pdf is not included in the payload if the webhook payoad exceeds 10MB.
The signed PDF is also goverend by some settings in the Sign account. There's a setting to keep documents seperate. If that is selected, the signed pdf in the webhook only includes the first uploaded document.
So by using API call instead you'll have more control on exactly what get's downloaded.
Copy link to clipboard
Copied
Hi @SimonESATS ,
Thanks for your reply !
Our initial design was also to call the combinedDocument API once we recevie the Webhook call.
But we have one concern here. Since AdobeSign uses OAuth with Autentication code , by the time we call the combinedDocumentAPI our initial access token will be expired. Now to call combinedDocumentAPI it first needs AuthenticationCode to get the access token, this authentication cannot be perfomed since this is running by the service and not a user.
So our question is - for sceanrios where user is not involved, what other authentication ways does AdobeSign provide us to connect to API other than using Autentication Code.
Copy link to clipboard
Copied
You can refresh the access token automaticlly, see https://secure.eu1.echosign.com/public/static/oauthDoc.jsp#refreshRequest
Copy link to clipboard
Copied
@SimonESATS Refresh token wont work for us. Currently we have a limitation in the tool we are using, it accepts only a single url for accesstoken and refresh token. But adobe sign has got 2 different urls for access token and refresh token.
Considering our sitatuion is there any other way we can use to authenticate all the time ?
Only approach we can think of is using legacy IntegrationKey method (By passing the integration key as Authorization header in every API call). But this will be our last choice.
Copy link to clipboard
Copied
@SimonESATS . Also Does Adobe Sign support JWT Authentication or does it just support OAuth alone?