pbradstreet

Hi, thanks very much for your response. As it turns out I finally fixed the issue yesterday. It turns out that the issue was more related to my application that received the webhook post. We are using WordPress multisite and I use the collection url to know which client website the webhook was submitted by. If the Collection url did not match my stored client collection url in our app it returns an error since that means that the submission did not come from a valid client.

The actual issue if anyone ever has a similar issue is that the automatically fired webhook uses the resolved domain name but if you manually update the order fire the webhook, the submitted collection url is the sub-domain version of the url. So I now compare to both possible variations of the collection url and it is working perfectly now.

Hi, Sorry which code are you referring to?