Web hook doesn't send Signed agreement document attributes in the response

Forum|Forum|4 years ago
October 16, 2021
2 replies
955 views

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_events/agreement_action_completed.md

Can someone let us know how and when will "Include Signed Agreement" Notification parameter work.

SDK

W

wesley_9326

Participant

So there is still no update on how to get this flag to work properly? I too have

"includeSignedDocuments": True,

and I am never receiving the base 64 encoded document. I get there is another API that I can call, but it would be very convenient if this functionality would just work as intended.

Also, I'm overall just struggling to find accurate documentation over what fields I can expect in this notification payload - especially when the different flags are activated.

Meenakshi Negi

Legend

Hi wesley_9326,

Thank you for reaching out.

We have checked your account with the email address you used to sign in on the community page. We cannot find any account with the email address.

If you have an Acrobat Sign Enterprise account with an alternate email address and have an integration-related question, the experts can best answer it. Please contact our Adobe Sign Enterprise support team for the correct information. You may contact them using the steps in the following help document: https://adobe.ly/4iiGHgO.

If you have the developer account, you may contact the pre-sales team. They will be able to provide you the pre-sales technical assistance and share the correct information. Please refer to the following link to contact them: https://adobe.ly/3D5Uit9. You may use the Contact Us button for Adobe Sign Solutions under the team tab.

For information on Acrobat Sign Integration refer to the following help document: https://adobe.ly/3Xmyz73.

Thanks,

Meenakshi

S

SimonESATS

Adobe Employee

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

get /agreements/{agreementId}/combinedDocument

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.

V

varun5E81Author

Participating Frequently

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.