Cvijo

[frozen cedar]

Hello, you are correct. At the moment you can't filter out events by accounts for certain IPs/URLS. All of your connected account endpoints will receive events for all connected accounts, so the server code itself will need to do the filtering

[sand crystal]

but i see problem here since i will have to generate xx number of webhooks on my platform account and stripe will send events to all of them but only one will return 200 OK

rest will still retraing to send it

[frozen cedar]

All of them should respond with 200s, even if the event is not relevant to them. The 200 is only for the specific URL, so if all of the servers but one respond with 200s and one 400s or 500s, we will still resend to just that server that had a failure

So you can be sure that the proper server will always gets the update and the servers won't interfere with each other getting the events

[sand crystal]

oh i see .. so even if i recive event on server i dont need lets say i will have around 158 endpoint hooks than and event checkout.session.completed will be sent to 158 of them even only one need to get this event but i will have to retrun 200 ok with all of them

Mybe in some future you might consider to add this feature to filter connected accounts web-hook endpoints to specific connected accounts 🙂

[frozen cedar]

Yes, the expectation there would still be that all 158 endpoints respond with a 200, it is expected to be an acknowledgement that the server got the event.
And I will file feedback about that. I have definitely seen this kind of functionality requested before, unfortunately I don't know what work if any is being done there.