#kpolsonslalom
vague halo
hexed marten
Hello, this is definitely possible. If you are using automatic payouts we even have a code snippet for this in our public docs: https://stripe.com/docs/expand/use-cases#charges-in-payout
If you are using manual payouts I can look in to how that would work as it is a bit more involved
proper dust
Thank you for the information! We are using automatic payouts, so that will work if I want to extract transactions for a specific payout. My goal however is to list all of the transactions and identify the payout for each, rather than list all the transactions for a particular payout
hexed marten
Ah gotcha, unfortunately I don't think that is currently possible in the API but will double check. If it isn't possible that way, you can still list your payouts and then to a list balance transactions call for each payout.
proper dust
Yeah, that might be what we have to do
For context, we're looking to load this data into a data warehouse, so if we can just extract all our balance transactions and all our payouts then reconcile them without a separate set of API calls that would be ideal
But if we need to go through that process to get the transaction ids corresponding to each payout that wouldn't be the end of the world
On that note, if I do go the route you described, is there any way to limit the attributes returned for me to make the API calls a bit more performant? For example, could I just request the balance transaction ids and exclude the rest of the details?
hexed marten
Good question. I don't think there is but I have seen our dashboard pass some parameter to only get an ID back. Will check if that is a general hidden argument in the API
Unfortunately it looks like balance transaction objects don't have a payout property and I'm not seeing another way to expose that data so I think this may be the way you have to go for now
Will put in feedback to expose that info though the balance transaction endpoint though