#kasturi-more_api
tulip breachBOT
👋 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/1364293873589030913
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
flint plover
hello! i am not aware of a way to do that off the top of my head - let me poke around and test a few things
are you doing automatic or manual payouts? if you're doing manual one quick solution might be to just include the account ID in the payout metadata
split hazel
Could you please elaborate on manual vs auto?
Also, if I understand your question correctly. We are not doing manual payouts.
flint plover
automatic payouts are scheduled to run automatically on a periodic basis, whereas manual payouts require you to call the Create a payout API.
automatic payouts:
https://docs.stripe.com/connect/manage-payout-schedule
manual payouts:
https://docs.stripe.com/connect/manual-payouts
split hazel
yes. We do automatic payouts only
flint plover
gotcha. let me see if we can get this info via expansion somehow...
https://docs.stripe.com/expand
any chance you have an example payout ID you've been testing with that you can share?
split hazel
It's list payouts. so we are trying to fetch all payouts created after a certain date
flint plover
i think expanding on destination should work
expand[]=data.destination
can you give that a go real quick?
IIRC the list payouts API doesn't list payouts across multiple accounts though... are you trying to run this on your platform account to get data for all of your connected accounts?
split hazel
yes
We implemented so we pass client type - test or live and fetch all the payouts associated with related weave xlient type.
Wouldnt that work?
flint plover
i am not really sure with weave and how it integrates with stripe, so i can't speak to that side of things
but the expansion parameter i suggested earlier should work to get you the destination.account value
split hazel
ok. But when I see the response for get destination, it does not have account ID either
Let me know if I am looking at the wrong object
flint plover
can you share an example request ID from a request you're making?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
also as i mentioned before an example payout ID will be helpful in telling me how you're setting some of this up under the hood
split hazel
Here's an example Payout ID - po_1RGapTHKaDXxdR6Ss8bQQPMz
flint plover
and can you share an example request ID where you called the List payouts API and expanded on data.destination?
split hazel
I didn't made a request for above.
flint plover
ok cool! want to give that a shot and let me know if it works? i tried on my test integration and it returned the account ID in the destination property
split hazel
Could you please share a screenshot of a response you received?
split hazel
okay. I'll give it a try. Thank you! 🙂
flint plover
yep of course! if it isn't returning the value feel free to come back and include an example request ID
split hazel
sure