#itaied-cli
vital gulch
hi! you can write your own fixtures that call the API in certain patterns to generate events you're interested in https://stripe.com/docs/cli/fixtures
errant stream
hi thank you!
One more question please, I'm using Stripe Connect with Express connected accounts type.
How can I attach the account id field to the event data both locally and in live mode (for webhooks)?
vital gulch
it's attached automatically when an event is generated on a connected account
to generate an event on a connected account you generally use the --stripe-account option in stripe-cli calls or API calls so that the API call processes on the connected account and all objects involved in the request are generated there
errant stream
using on_behalf_on or destination transfer doesn't attach this parameter?
vital gulch
generally no, since in a Destinaation charge all the objects like the PaymentIntent/Charge live on the platform account so all the events that relate to them are generated on the platform account and don't have the account field set and are not sent to 'Connect' webhook endpoints
it doesn't generate payment_intent.succeeded events on the connected account for example if that's what you expect, that's not how Destination charges work