#ezra_webhooks
mortal pawnBOT
👋 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/1458556121127190579
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
charred torrent
No webhook here...
But there is here
Wait-- I just double checked and my webhook for thin events on my account wasn't set up for v2.account.*, which I guess was the issue. BUT on local, using the webhook forwarder, I was able to do everything I needed to using snapshot processing for webhooks, not thin event processing.
Is it different in production?
Can I not get snapshot events for v2.account.updated? Even though I can with the webhook forwarder?
Or, can I get account.updated events instead of v2.account.updated?
Because I was able to do that locally using the forwarder
astral scarab
Hello, looking in to this. Can you tell me more about your overall goal here? Are you trying to get both versions of all of these events? And is this for testing how these work mostly, or is there a broader thing you are trying to do with these events?
charred torrent
I need to process account.updated webhooks to determine if a user has finished onboarding to Stripe Connect
I've implemented snapshot event processing for this
But not thin events
I don't care about receiving thin events (at the moment, anyway). I just enabled those to debug
astral scarab
Ah gotcha, I think I see the problem here. The endpoints you have registerred so far are Account endpoints, so they only receive events that happen directly on your account. If you want to get events for your connected accounts you can register a Connect endpoint: https://docs.stripe.com/connect/webhooks
Basically "Direct" vs "Connect" is a choice you can make when creating your endpoints, you need to choose connect along with the account.* events that you are interested in
astral scarab
Ah yep that should work. I just checked the account associated with evt_1SmNj2GliZed6nmO50ADmPzf (looks like the other ID you provided may be two IDs merged in to one). Can you try sending me an account event that your connect endpoints did not receive again?
mortal pawnBOT
astral scarab
It looks like the account for that event (acct_1SXrpVGliZed6nmO) isn't connected to any platform accounts. How did you try to create/connect that account to your platform?
charred torrent
I'm not sure what that means.
dusk prawn
Hello 👋
Taking over as Pompey needs to step away soon
charred torrent
Hello! Thanks @astral scarab
dusk prawn
acct_1SXrpVGliZed6nmO is the platform right?
charred torrent
I guess so? The dashboard is https://dashboard.stripe.com/acct_1SXrpVGliZed6nmO/dashboard
dusk prawn
In your thin-two destination, what types of events are you listening to?
charred torrent
v1.billing.meter.no_meter_found
v2.core.account.closed
v2.core.account.created
v2.core.account.updated
v2.core.account[configuration.customer].capability_status_updated
v2.core.account[configuration.customer].updated
v2.core.account[configuration.merchant].capability_status_updated
v2.core.account[configuration.merchant].updated
v2.core.account[configuration.recipient].capability_status_updated
v2.core.account[configuration.recipient].updated
v2.core.account[defaults].updated
v2.core.account[identity].updated
v2.core.account[requirements].updated
v2.core.account_person.created
v2.core.account_person.deleted
v2.core.account_person.updated
v2.core.health.event_generation_failure.resolved```The thin event webhooks I mostly created for debugging. The real issue is that I want to be getting account.updated (and all the other webhooks) as snapshots
This was working locally using the CLI local listener
mortal pawnBOT
Hello @charred torrent, we have sent you a direct message, please check it at https://discord.com/channels/@me/1458564594107678811
- 🔗 The message has instructions on how to grant read and write access to your Stripe Dashboard for our Developer Support team, in order to help you more effectively.
dusk prawn
Can you approve the consent so that I can take a look at your dashboard settings?
dusk prawn
Thanks, taking a look
charred torrent
Thank you!
dusk prawn
So v2.core.account.created would be generated on the account/platform level. So by design, you would be expecting the event to be generated and delivered on the account level webhook
So we'd expect it to be delivered on production-webhook-thin destination
charred torrent
Can I get it as a snapshot event instead of a thin event?
I was able to process it as a snapshot event in local dev using the stripe CLI
dusk prawn
For V2 accounts, I don't believe you can.
Snapshot events are only generated by V1 endpoints (so V1 Accounts API)
charred torrent
Do you know why that's different than what I saw when doing local development with the CLI?
dusk prawn
How did you generate these events?
charred torrent
Do you know why that's different than what I saw when doing local development wi...
and how do I use the cli to forward thin events, for local development?
dusk prawn
I mean via CLI
charred torrent
How did you generate these events?
The same way I did in production -- by clicking around the website (running on localhost). So ultimately by using the typescript library
dusk prawn
Do you have any example events where you generated snapshot event for a V2 account?
charred torrent
Checking
evt_test_65TtxxSSTQ5Su260lCM16ThFnJBdSQKct72a4sb48m06g4 I think this for example
This is a test event on the sandbox account
dusk prawn
that's a thin event as well
charred torrent
1 sec let me trigger one on my dev environment
mortal pawnBOT
charred torrent
Can you help me with this CLI error?
The docs say * should be allowed here
west pier
Hi there - taking over for hanzo
let me have a look
seems like you need this:
stripe listen --thin-events '*'
charred torrent
ah, thank you. I tried "*" but that didn't work. maybe worth clarifying in the docs
west pier
interesting. "*" works fine for me; might be related to the shell you use
charred torrent
seems like you need this:
`stripe listen --thin-events '*'`
Actually, I get this warning using this command:
ezranewman@Ezras-MacBook-Air ace-next % stripe listen --thin-events '*' A newer version of the Stripe CLI is available, please update to: v1.34.0 [Wed, 07 Jan 2026 17:16:02 EST] INFO Warning: You're attempting to listen for "*", which isn't a valid thin event or preview event
west pier
That's interesting. It just works for me. Noted