#avinash_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/1347499015033458702
๐ 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.
- avinash_payment-refund-metadata, 1 day ago, 70 messages
- avinash_api, 1 day ago, 28 messages
Hello,
๐ happy to help
Unfortunately you can't decide what information is available in the expanded object
you can expand but not restrict
it's not like graphql
Let mtry explain - We have called balance transaction api and expanded to get more details from payment intent and refund object ..due to this we are getting 300+ line items in each transaction so i am trying to see if in that API call , can I put criteria to get only required data in payload
criteria like what?
We are interested in getting roughly only 10 dataset (like Payout number, amount, report category , creation date, meta data ....) in that payload
that's not possible as I explained earlier
ohh...we are using
yes, you can remove the expand...
THe reason we used this because we wanted to payment reference of refund and associated payment ref of original payment
I'm not sure why the response size is an issue for you though?
it's better to expand and get everything within one call than to make multiple API calls