#orelzman_api
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/1310994883359670403
๐ 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.
- orelzman_api, 2 hours ago, 33 messages
This is not the recommended way to listen to events for connected accounts
Instead, you should create a COnnect-type endpoint on your platform account, which will receive events emitted from connected accounts
What am I missing?
Ah insteresting, I looked too quickly and focused on the error you shared
Are you setting a stripe-account header/option somewhere?
This error suggests you're trying to create the endpoint on the connected account, not your own account
How are you initializing stripe-node here?
Ah, right, that
You need to remove that stripeAccount for the endpoint creation
You can also create this endpoint in your dashboard
Oh, wait
(connect type for your own platform account)
So I create a webhook for connected accounts
which means that I have 1 webhook for all connected accounts?
So if Bob triggers and event and Eve triggers another one, will they both go through that webhook?
Yes, that's correct
the event will have an account attribute to identify which account it came from
Fantastic! I am testing it right now ๐