#vincent_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/1293681650789777440
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- vincent_account-requirements, 1 hour ago, 11 messages
- vincent_docs, 2 days ago, 9 messages
Hi there! Looking into this now
thanks ๐
Okay, so it looks like this capability had already been requested in a different request about 13 minutes earlier. Here's where that happened: https://dashboard.stripe.com/test/logs/req_Lif6vYg2XtmuvH
Since req_P2H5uj2p28bNcp didn't change anything (capability was already requested), it didn't generate a webhook event. Here's that first capability.updated event: https://dashboard.stripe.com/test/events/evt_1Q83u0HfpsBXgSnlFIToqLrH
Hm, I can't seem to see that event. I see this when I visit https://dashboard.stripe.com/test/events/evt_1Q83u0HfpsBXgSnlFIToqLrH
however, I did see this event on the connect account which seems to be correct:
https://dashboard.stripe.com/test/events/evt_1Q85BlLdJVNsLKhod7iy5O5B
if the events for connect accounts are sent to the same webhook endpoints as the platform account events, then that should be sufficient! can you confirm that that is the case?
you know, i just found that my webhook did not have the capability.updated event enabled
That's right, so if you navigate to the connected account that this request was made on, then you would be able to view this event from the list of events on that account. The event "lives" on that connected account.
Any Connect webhook endpoints that you've set up should have received this event.