#Arnaud Lier
twilit coral
charred tree
Is that endpoint set up to listen for Connect events? When Connect is involved, you need 2 separate endpoints. 1 for Connect account events and 1 for platform events
dense sage
Is that endpoint set up to listen for Connect events? When Connect is involved, ...
Whoops, thought these events were being attributed to the Connect accounts! Thank you for your time 😄
So we need to check for two different signatures?
In my tests I thought it worked with only the Connect endpoint but maybe I was just listening with the CLI
charred tree
So we need to check for two different signatures?
Correct. 2 endpoints with 2 different signatures
dense sage
Would be nice to receive both on only one webhook 😄
mental horizon
Because the events are fundamentally different in nature, they are separate
I'd recommend having two different endpoint myself
But you can have "two endpoints" that differ by only a query parameter, eg
then you can use that query param to decide which signing secret to use
dense sage
That's what I was going for, thanks again!
Probably the best developer documentation and support I've never seen 🙂
mental horizon
🙌