N0xB0DY

[short eagle]

hi there

Will I still be able to receive the connected webhooks events in the same way the CLI does?
Not sure I'm following what you mean here,
Each Webhook endpoint will receive what you've configured to listen to.
If you setup another webhook and you choose your account instead of connected, you'll receive your account related events

[cyan axle]

On my dev environment, I setup the CLI to forward the hooks to my API using -f https://mylocalurl/.

and I was able to receive all events ,as account.created and checkout.session.completed

[short eagle]

You should be using stripe cli forward for your local url, the screenshot you are using is for creating a webhook endpoint that is hosted

[cyan axle]

I know, the idea is, after setting up the cli for localhost, I was receiving both type of events to the same URL.

the connected events and my events

Is it going to be the same behavior if I choose my account instead of connected?

[short eagle]

Sorry, still not understanding your request yet.
But, there is no link between stripe cli and the options in the screenshot you are sharing above.
If you want your stripe cli to get only the connect event use the option --forward-connect-to
https://stripe.com/docs/cli/listen#listen-forward-connect-to

I invite you test the scenario when you create webhook and choose your account event:
here is more details about the difference between Account and Connect webhooks:
https://stripe.com/docs/connect/webhooks#connect-webhooks

[cyan axle]

Sorry, let me put this way.
If I create a checkout session for a connected account. and the session is completed.
Will stripe sent the checkout.session.completed event to both endpoints type, my account and connected accounts, or just the connected accounts?

[woeful yarrow]

Just the Connect endpoint

[cyan axle]

Thanks