#juicy28-webhooks

1 messages ยท Page 1 of 1 (latest)

empty lance
#

hi there, you mentioned that it was working earlier, did you happen to change anything recently? e.g. did you just deploy to production?

orchid spade
#

Nothing particular to the particular webhook. Thanks for the help.

empty lance
#

I'd suggest first logging the webhook secret key when your server is running and attempting to process the webhook event to ensure that you have the correct webhook secret key set

orchid spade
#

I checked and its correct ๐Ÿ˜ฆ

#

Will the secret expire in any case?

empty lance
#

no the secret won't expire

#

can you share how you checked? So you added a console.log line in your server code, ran your server, and triggered a webhook event, and you verified the webhook secret that was printed in the terminal / console?

#

can you share the code snippets that you're using to process a webhook event?

#

you'd want to redact all sensitive information such as secret keys before sharing it here

orchid spade
empty lance
#

do you have any middleware before that? can you share that too?

orchid spade
empty lance
#

is the express.json middleware being used for the requests for the webhook endpoint?

#

because the express.json middleware does change the request body

orchid spade
#

Thanks for taking a look into this for me @empty lance , It looks like I now know where the issue is. ๐Ÿ˜