#Cvijo

1 messages · Page 1 of 1 (latest)

vestal irisBOT
heavy depot
#

Are you referring to events from connected accounts, and determining which account it is related to?

frigid elm
#

yes for connected accounts but i know i get info on events wich account it is

heavy depot
frigid elm
#

problem my platform has for each of my client its own domain

#

so i will have to create 200 webhooks

heavy depot
#

No

#

You receive all events to /connect-events

#

then your endpoint can inspect event.account and see which account its from

frigid elm
#

problem is those 200 accounts are not connected between so i am not able to listen to one endpoint and act on event for another endpoint

#

i am not sure if i am explaining good

#

but as i said i have 200 clients each on his own domain and my backend is on each of them

#

so if client 1 create checkout session i have to recive webhook on that client 1 endpoint

#

and if client 2 create chekousession i have to get webhook fired on client 2 domain endpoint

heavy depot
#

You should be operating one central connect endpoint on your own infra and managing the connect events there

#

Connect endpoints will get events from all connected accounts

frigid elm
#

that is problem i cant manage on one endpoint for all connected account .. i have alot of servers across countries (28 countries atm) and they cant communicate to eachother .. not all of them so if i get 1 server to recive all my connected accounts events (lets say i put this server in country A, i am not able to do anything with that event if it is for server in Country B)

heavy depot
#

Your particular setup might require you to forward events or send your own events to client servers

#

But connect endpoints are expected to be operated centrally by the platform, not each connected account

frigid elm
#

for me to work this i have to create 200 webhooks for each client and response 200Ok with all of them

heavy depot
#

Setting up 200 is not possible

frigid elm
#

oh .. that is problem now i see .. major thing i understand what you are saying but i am unable to send events from country A to country B .. its a bit complicated to explain about some policy and rules among clients

#

its seams that this is now a major problem with design and how to forward those events to different servers, but if i am limited to 16 endpoints than i dont have solution atm i guess

heavy depot
#

Yea, I think you'll need to revisit the architecture here and ensure you receive these events centrally. It might be that you need to operate with accounts/servers regionally if you are subject to rules that prevent you relaying events globally

frigid elm
#

yeah .. back to the drawing board i guess .. thank you synthrider