#coldsteel_webhooks-beta-header
lone ginkgoBOT
👋 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/1327026902426320916
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
old owl
Yeah, you're ultimately going to have to create a new webhook endpoint for testing this beta and specify the api version as the beta version outlined in the error message you got.
crude compass
Okay; so theres no way to add the beta flag to an existing webhook endpoint? It has to be a new one?
old owl
The api version of a webhook endpoint cannot be updated: https://docs.stripe.com/api/webhook_endpoints/create?lang=node
crude compass
I assume there is no way to add the beta version to the default api version either?
old owl
Not that I'm aware of, but we aren't super familiar with most betas in this server. If you were invited to a private beta you were likely given a support contact where you can go with questions specific to the beta.
lone ginkgoBOT
sick bobcat
Hi 👋
I'm stepping in as my colleague needs to go soon. What they have said regarding api headers is correct.
Generally, we recommend creating a new webhook endpoint if you need the beta header specified
Especially since, if the beta feature becomes generally available, you would want to remove that header later on.
It is easier just to delete the webhook that uses the beta header
crude compass
Alright thank you for the help. We will make a new webhook endpoint for the beta feature then.