Copy link to clipboard
Copied
Request URL
https://api.sg1.adobesign.com:443/api/rest/v6/webhooksResponse Body
{ "code": "INVALID_WEBHOOK_URL", "message": "Validation for webhook url failed. Please make sure that the webhook url responds with a valid HTTP response code and a valid client id." }
Data:
{ "applicationName": "Test application", "name": "Somename - 5c0bc93d-b955-4451-bbc1-3b7e92c1cd6c", "state": "ACTIVE", "scope": "ACCOUNT", "webhookSubscriptionEvents": [ "AGREEMENT_ACTION_COMPLETED" ], "webhookUrlInfo": { "url": "https://www.sqlviewhz.com/KRISADMIN/adobesignCallback" } }
URL can be accessed, webhook configuration failed
1 Correct answer
I suspect the webhook may have been created via the webportal, rather than via the API.
In that cas the clientID to use is the clientID of the Sign webportal which is
UB7E5BXCXY
(it should also be in the header of the GET request itself)
Copy link to clipboard
Copied
how does the url respond to the initial GET request Sign pings the url? and how will it respond to POST requests following that? See https://www.adobe.io/apis/documentcloud/sign/docs.html#!adobedocs/adobe-sign/master/webhooks.md
The webhook willl send a GET request to the url in order to verify it. It expect a 200 response and the clientID as a response.
If done correctly the same response is expected for the POST notifications.
Copy link to clipboard
Copied
Hi SimonESATS,
Thank you for your reply.
Our URL supports GET and POST request access
The URL I provided is Java Restful. Is there any requirement or attention to the Java project?And I can get that Adobesign requested to visit my URL and returned.
Thanks.
Best Regards.
Copy link to clipboard
Copied
1.POST
2.GET
Copy link to clipboard
Copied
I suspect the webhook may have been created via the webportal, rather than via the API.
In that cas the clientID to use is the clientID of the Sign webportal which is
UB7E5BXCXY
(it should also be in the header of the GET request itself)
Copy link to clipboard
Copied
Yes,except for Java REST API, I tried other URLs with success. But there is one point I noticed: response.setHeader("X-Powered-By","Express"); 'X-Powered-By' must be 'Express'.
I set it to ‘Undertow/1’, the setting will also fail.

