#sambindoff
glad geode
hello! let's start here
I'm still receiving events occurring on my platform account, not the connected accounts.
let's try basic test
Q) Create a Customer object on a connected account and share the request ID (or Customer ID) of the request and let's go from there
open bone
Hey @glad geode sure, thanks for the help.
Request req_vYlLnoEWHIxPM0
Customer cus_O9eya8lyzdqeAL
glad geode
that's on the Platform actually, and through the Dashboard
try one using the API
and passing the Stripe Account header, I assume you're familiar with that field?
open bone
The request and customer above was performed on a connected account (Bindoff Limited acct_18eQMJC8n7k4iuLS) associated with the platform account (DoDays acct_1ANIgXBnq82pICHb)?
New customer created over the API:
req_xctik1yb3FOxEg
cus_O9fD8POsChzA7f
glad geode
The request and customer above was performed on a connected account (Bindoff Limited acct_18eQMJC8n7k4iuLS) associated with the platform account (DoDays acct_1ANIgXBnq82pICHb)?
it was not a Connect request though, it was created directly on the connected accounts Bindoff, so just making that distinction. It should still result in Connect events but was just simplifying the problem.
Looking
ok great so https://dashboard.stripe.com/test/logs/req_xctik1yb3FOxEg is a Connect request, made by the Platform on the connected account, great
now let's use that as our testing bed - I'm assuming that did not result in a webhook event on your CLI?
open bone
Nope, no new events in terminal
glad geode
ok let me spin up CLI with Connect events locally, one sec
robust oceanBOT
glad geode
ok so
just did
stripe listen --forward-connect-to http://....
and created a Customer on a connected account and it worked, here's what CLI said:
--> connect customer.created [evt_1NNMLcKCSfvepfXZZNPBqAxT]
so the same CLI command as yours works
open bone
🤔 and you signed into the platform account before listening right?
glad geode
yes
the same CLI instance also gets
--> customer.created [evt_1NNMPlDPNvtYYWA7lUzrqsli]
which doesn't have the connect annotation since it was created on the Platform
open bone
What do you mean by connect annotation?
For your event under Webhook CLI responses do you see an entry?
Also, does your webhook payload contain an account property which is the ID of the connected account?
open bone
Gotcha
So I'm just not receiving the connect events
Would --forward-to also receive connect events, or only platform?
glad geode
@sleek axle my colleague is here and will hand off to them, they can help you
open bone
Ok thanks for your help so far @glad geode
sleek axle
Hello! I believe --forward-to only forwards your own account's Events.
open bone
Understood
Hold the phone, looks like my platform account has no connected accounts...
sleek axle
Well, in that case you absolutely will only get your account's Events. 😅
open bone
I should stop being so OCD about deleting that test data!
Sorry for wasting your time today, have a great rest of your day
sleek axle
Not a waste at all, we're here to help!