#piercy_webhooks

1 messages ¡ Page 1 of 1 (latest)

ocean jacinthBOT
#

👋 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/1324697180359102536

📝 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.

tardy tiger
#

hi! well your 'normal' webhook gets account.updated events that happen on your own platform account about any changes on it; your Connect endpoint gets account.updated events that happen on connected accounts when things on change on them.

solar saddle
#

As an example, I am trying to listen for accounts being created (ie, completing the onboarding form)

#

It looks like that might only be on the connected events

tardy tiger
#

yes

solar saddle
#

Well.. that's fun.

#

As a note, the CLI forwarding doesnt seem to follow this behavior. It forwards account.updated for connected accounts.

tardy tiger
#

I'm not sure what you mean by that. Something changes on a connected account. We generate account.updated. If the platform connected to that account has as Connect endpoint, we send the event to that. If the platform is using stripe-cli and the --forward-connect-to option, we send the event to that location too

solar saddle
#

Ok i see how that works, I understand its documented, but to use test mode as an example, its expected that test mode works the same as production (especially as production testing is frowned upon).

This feels like one of those cases where the expected behavior is that it works like production. A note in the documentation - while it should have been seen - it goes against the general understanding that things work the same as production

#

Missing this event has caused quite a big problem for us, and this would have been seen had the CLI worked the same as production and be platform or connect specific.

Ill work on a resolution, I should be able to work something out