#troymeout_webhooks
1 messages · Page 1 of 1 (latest)
👋 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/1245185456589508661
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! you will need to create the webhook via the API if you want to explicitly define a version : https://docs.stripe.com/api/webhook_endpoints/create#create_webhook_endpoint-api_version. It’s not possible to do so via the Dashboard.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Okay thank you
So oddly now I'm getting "Stripe.StripeException: The signature for the webhook is not present in the Stripe-Signature header."
I verified that the signing key is correct. Is there a reason why Stripe wouldn't be sending it?
did you use the correct webhook secret?
whsec one yeah
i would log it out to be sure. To clarify, when you create a new webhook, the webhook secret is different. Also, if you're forwarding the webhook using the CLI, you should be using the webhook secret defined by the CLI
Yeah, not using the CLI and I know I got a new secret when i created the new webhook
if you've validated that and it's fine. The other likely reason is that you're not passing the raw request body into constructEvent
are you using ExpressJS?
Well the request should be working because the same code is working in our production environment (Obviously with a different secret key).
Does the Test environment always send the signing key too?
yes, the test environment will always send the signature
If so, i can create some logs. Maybe there is a caching issue somewhere on my end with the key.