#shenstath_webhooks
uncut shardBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1336211701774680107
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
knotty iron
Hi! The event provided has a 200 HTTP status code from your server. Can I check if that event was verified manually?
pastel sail
The event is not verified manually
knotty iron
Could you provide me with your code for how you manually verify the webhook?
pastel sail
I cant provide code for security issues 😓, but when i tried validating online through multiple hmac tools, i was not able to verify
In code also its not verifying
knotty iron
Can you paste the event ID here please? Thanks!
Could you also give us the tool you are using?
pastel sail
evt_1QoblBQEpmOqHln1rloK19UE
Thanks for the assistance bro
@knotty iron here is the tool and id
knotty iron
Thanks!
knotty iron
From the screenshot I can see 2 issues:
- The wehbook secret must have whsec_ at the start
- The payload cannot be stringified. It has to be as it is received.
pastel sail
@knotty iron i have used whsec_ key, i have also used non stringified version but still
iam not getting that verified
knotty iron
We have tested it internally and have been able to get the correct signature scheme. Can you send me a screenshot of your latest attempt?
pastel sail
knotty iron
You need to paste the payload as you get it. Above looks like a stringified version.