#haddock_webhooks
quiet cosmosBOT
đ 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/1438625699547058187
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
thick prairie
we see the event getting consumed twice in the API at the same time
What do you mean by that? Webhook events are POST requests from Stripe to your server
For the event you shared, I see this event is being delivered to 7 different webhook endpoints.
Delivery is failing for 2 of them:
https://api.control.staging.coalitioninc.com/webhook/stripehttps://api.control.dev.coalitioninc.com/webhook/stripe
When an event delivery fails, we attempt to re-send it multiple times until we either get a 200 response or it exceeds the max retries.
If we see several failing event deliveries we will eventually disable the webhook endpoint
ashen field
where I can see the 7 endpoints configured ?
I can try and have this limited to 1 and test this again
thick prairie
They should all be on your dashboard, since none of them are Connect endpoints
We moved from api_key to endpoint_secret fpr webhook events and have started seeing 200 and a 400 for the same event
Do you mean that when you attempt to verify the signatures this is failing?
I recommend you review our guide to signature verification here: https://docs.stripe.com/webhooks/signature
ashen field
Thanks , we found the issue. the same webhook endpoint was used twice one with endpoint_secret and the other without. Disabled the one that was failing and tested the event publish, it works now.
why is there no validation when we try to add the same webhook endpoint twice ? Is this designed on purpose ?
thick prairie
I cannot speak to the specific design process but, generally, Stripe has been designed to allow greater flexibility on the assumption that developers know what they are doing.
ashen field
Docs dont call it out and is not somethign to be assumed off
thick prairie
Well I recommend you review your existing webhook endpoints before creating new ones in that case
quiet cosmosBOT