Skip to main content
C
crazyhor77
Participant
April 9, 2019
Answered

Webhook Help

  • April 9, 2019
  • 2 replies
  • 2174 views

I think I'm having trouble getting my webhooks to fire.  I have setup a generic endpoint which works with my fiddler testing.  I am extracting and returning the client id in the header request/response as stated in the documentation.

Is there any way to see if my webhooks have fired?  Are there any logs I can check?

My webhooks fire on all events and my endpoint simply accepts any generic information so I have made it as simple as possible, but it's not firing.

Would appreciate any suggestions.

This topic has been closed for replies.
Correct answer SimonATS

Staff access, you should also see this in your web server logs. Having said that looking at the logs for the webhook subscribed to all agreement event, I now see successful requests.

2 replies

P
Prakash25595782czzh
Participant
August 12, 2022

Hi,

 

Please tell me how to read Webhook POST api call. I want to know whenever Webhook makes a POST call using webhook url, how do i read Agreement Id and the event for which it has triggered/called. 

 

I am using C# Web Api for Webhook POST method. 

S
SimonATS
Legend
April 10, 2019

assuming you setup a dev account using the same email address as your forum user here,

The webhooks have been created and are active, however each post request is met by a http 405 respone (method not allowed)

From

Wbehook Documentation

How to respond to a webhook notification

Adobe Sign performs an implicit verification of intent in each webhook notification request that is sent to the webhook URL. Every webhook notification HTTPS request contains the customer HTTP header called X-AdobeSign-ClientId. The value of this header is the client ID (Application ID) of the application that created the webhook. We will consider the webhook notification successfully delivered, if and only if a success response (2XX response code) is returned and the the client ID is sent in either the HTTP header (X-AdobeSign-ClientId) or in a JSON response body with key as xAdobeSignClientId and value as the same client ID; otherwise, Adobe Sign will retry to deliver the notification to the webhook URL until the retries are exhausted.

so to be clear to register the webhook is a Get request, but once active the webhook then makes POST request to deliver the payload.

C
crazyhor77Author
Participant
April 12, 2019

Thanks Simon, I tried changing the api to accept POST requests but still don't appear to be getting anything.

Where did you see the 405 responses?  Is this something I can check myself?

S
SimonATSCorrect answer
Legend
April 12, 2019

Staff access, you should also see this in your web server logs. Having said that looking at the logs for the webhook subscribed to all agreement event, I now see successful requests.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices