#ashish1751_webhooks
faint cometBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- ashish_subscription-renewal, 4 hours ago, 44 messages
shrewd crownBOT
đ 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/1270512658222809088
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sly yoke
Hi there
Hm, I'm not familiar with Hono
taking a step back, if you remove signature verification temporarily, can your endpoint receive the event?
mellow sand
Yeah I'm facing trouble with verifying the body
That's what apparently constructEvent does, right?
sly yoke
Correct
Typically, that error points to either using an incorrect signature or that a library or other third-party tool is not using the raw request body
Note that the signature for webhook endpoints you see in your Dashboard is different from any CLI signatures
mellow sand
Yeah, I checked that they are in same format as required that. I personally think it's hono is doing somwthing with req.text() be it indentation or new line, which I'm not able to figure it out