#oscadev_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/1340020498284675102
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi! That account ID doesn't have any webhook endpoints set up.
I am a developer for a company "PAAW". I setup a webhook for connect on that account. I then setup code to create links for anyone to be able to "connect". Then the user can go through the onboarding and the PAAW webhook should trigger. This worked in sandbox mode. I didnt have to create a webhook for each onboarded member, just one for PAAW
Cool. Which Account ID would show that?
You mean, what is PAAW's account id?
Yes.
acct_1KgyXYFsQu437g5S
This is the account where I created the api keys and webhooks, that users should be onboarding to, but 'account.updated' never fires even upon succesfull completion
That account has no Connect Webhooks.
mystery solved
Yup. ๐
Where do I add it. I dont remember, and it seems the developer / webhooks area doesnt ask me if it is a connect webhook or another type
Hi, I'm taking over as my teammate needs to step away. Let me catch up
thanks
We document this here: https://docs.stripe.com/webhooks#create-webhook-endpoint
Let me know what questions you have after reviewing the document
ok, so the way to declare that the webhook is a connect webhook is to choose "events on connected accounts" when creating the webhook, rather than "events on your account"
I thought that since they are onboarding to OUR account, it woudl still be "events on your account"
Thanks, I think that will fix it