Skip to main content
I
Ioan27158520a19d
Participant
February 19, 2023
Question

Testing Webhooks in Acrobat Sign

  • February 19, 2023
  • 3 replies
  • 1419 views

I am trying to set up a webhook for Adobe Sign according to https://opensource.adobe.com/acrobat-sign/acrobat_sign_events/index.html#managing-webhooks-and-subscriptions

 

Whenever I attempt to create a webhook by POSTing to /webhooks, I get back the following response:

{"code":"INVALID_WEBHOOK_URL","message":"The Webhook Url is either denyListed or the host name is not allowed Request id: cf05f2b1-203f-415c-986f-0d721904b04b."}

 

Since I am currently developing this webhook feature, I am trying to set it up using my local development computer. I verified over and over that the domain name I have set up for my computer is up and running and that I can access it from the world wide web and I also tried to use my IP address directly instead of the domain but I still get the error above

 

How can I get my url to not be "denyListed" or allow my host name?

    This topic has been closed for replies.

    3 replies

    A
    Adobe Employee
    Amol28780807vqz1
    Adobe Employee
    March 8, 2023

    Hi there,

     

    Thank you for using AdobeSign Webhook, sorry for the late reply.
    We were able to trace back the call you made back in Feb and see that the Webhook url you are using has non-standard port.
    Please visit our https://helpx.adobe.com/sign/using/adobe-sign-webhooks-api.html page and you will notice that we only support 443 and 8443 ports.
    The URL endpoint must be listening on port 443 or 8443 (decided by the customer when defining the callback URL).

    Please also visit https://helpx.adobe.com/sign/system-requirements.html#ipranges page for additional requirements.

     

    Hope this resolves the issue, do let us know if there is anything.

    Amol Pawar - Software Engineer - Adobe Acrobat Sign

    P
    Adobe Employee
    p s k
    Adobe Employee
    March 8, 2023

    I suggest you test your webhook endpoint from https://www.ssllabs.com/ssltest/ and look in the certificate sections of the report to verify that nothing is shown under "Chain Issues".  This will eliminate issues due to reachability of your endpoint and configuration errors with its TLS certificate chain that could prevent Sign from connecting. 
    (Note also that you must use a domain name, not an IP address, for TLS authentication to succeed.)

    atsmusz_as_dsEng
    Adobe Employee
    atsmusz_as_dsEng
    Adobe Employee
    February 21, 2023

    Hi there,

     

    Three things are required for webhooks to properly register.

    1. Publicly available domain name with valid 200 response from the FQDN+ page
    2. HTTPS (secure communication using tls 1.2 minimum)
    3. Correct indication of "intent" in the response

    Your endpoint must respond with either the x-adobesign-clientid in the response header, or `xAdobeSignClientId` + value in the response body for both the GET to register the webhook, as well as the subsequent POSTs once the webhook is registered.  It must continue to "echo" back this parameter in the header or the response body.

     

    If your domain, host, or page was not responding properly in the past and you attempted to register a webhook, the registration will fail. If the domain+host+page you attempt to configure does not respond properly for a limit of repeated attempts, the Sign platform will mark it as un-usable (denyList) since continuing to attempt connecting there eats up resources.

    Aaron Smusz - Data Science Engineering - Adobe Acrobat Sign
    I
    Ioan27158520a19dAuthor
    Participant
    February 24, 2023

    Thanks for the reply but I am not getting to that point. It's not even calling the endpoint. It is HTTPS, it is publicly available and it should return the xAdobeSignClientId in the body but It does not even get called.

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