Dwolla signs each webhook request with the secret you passed in when you created the webhook subscription. The signature is contained in the x-request-signature-sha-256 header and is a SHA256 HMAC hash of the request body with the key being your webhook secret.
You can validate the webhook by generating the same SHA256 HMAC hash and comparing it to the signature sent with the payload.
The proposed signature would be the value that’s contained in the x-request-signature-sha-256 header on the webhook request.
@spencer Hi! For some reason I stopped getting request from the dwolla webhook, I had gotten working but then while testing my API stopped getting the subscriptions from the sandbox. Any guidance on this?
spencer
(Spencer Hunter - Lead Developer Advocate @ Dwolla)
5
We can take a look in our webhook logs to see if we can find anything @Engineering_Archie. Do you have your subscription ID or your account ID? Thanks!
@spencer Following question, should I setup a separate webhook subscription for money involved transfers and customer onboarding status for businesses? Or can one serve both?
Also, wondering is there list with the possible topic response I can grab from?
Hi @Engineering_Archie – Actually, a webhook subscription will serve all events that occur on your platform. You wouldn’t be able to subscribe to specific event topics.
Yes – here’s a comprehensive list of all possible events in Dwolla - Dwolla API docs