#evan_cli-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/1222966366798352384
๐ 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.
- evan_api, 22 hours ago, 13 messages
Are you asking how to have connect events go to one endponit and account endpoints go to another through the CLI?
cool! you should be able to do this by specifying both --forward-to AND --forward-connect-to (see https://docs.stripe.com/cli/listen#listen-forward-connect-to)
๐
thanks for the help!
glad it was a quick fix ๐
evan_cli-webhooks
Just to clarify, is the expected way to handle this to call stripe listen once, and specify both --forward-to and --forward-connect-to? The events list would then be the superset of both endpoints?
--forward-to seems to forward both connect + account events
Yes you'd do it in a single call
By default --forward-to would control both, but when you specify --foward-connect-to it allows you to override that
cool! Might just be me, but I think it makes more sense if it was two separate stripe listen calls and --forward-to only handled account webhooks. It's more similar to the way the webhooks in test/prod are set up, and was a stumbling point when getting things working in prod
or, I could just do a better job of reading the docs ๐