Hi @shen_2585,
Hope you are doing well. Sorry for your experience with using webhooks.
Here is what I think could be a possible reason, and a perspective for you to get this working:
When you register a webhook in Acrobat Sign, it first sends a GET request to your endpoint to verify it before it can be used. This is part of its Webhook Verification process. Your endpoint must handle this GET request in a very specific way,
Steps I'd suggest:
Handle the GET verification request
-
When Acrobat Sign calls your endpoint with a GET request, it sends a query parameter called verificationCode.
-
Your API must read this verificationCode and return it as plain text in the response body, with HTTP status 200.
Keep your POST logic for actual events
-
After the verification succeeds, Acrobat Sign will start sending POST requests for real webhook events.
-
Your code should have separate handling for POST to process the event payload.
Re-register the webhook
-
After adding GET verification handling, delete the old webhook in Acrobat Sign and create a new one with the updated endpoint.
-
The validation should now pass, and events will be delivered via POST.
- More info here: https://adobe.ly/4mCwqhY
If you don’t handle the GET verification step exactly as Acrobat Sign requires, the portal will keep showing "The URL provided is not a valid webhook URL."
Hope this helps.