#GeorgeManderson
little rain
rough badge
technically it doesn't need to be one, and I could just parse their charge objects but Id rather just do one call and not have to parse at all.
regal geyser
It looks like you can use the disputed field in the search API for charges, so doing a search with that param and the customer ID should get the results that you want here https://stripe.com/docs/search#query-fields-for-charges:~:text=token-,disputed,-disputed%3A"true"
rough badge
Thanks, I'll take a look.
Looks like I can't search dispute objects directly, I can at least refine the charge object query to only include charges that are disputed. Thanks for the help.
regal geyser
Yes, unfortunately it looks like there isn't a way to do this with the disputes API directly so this should be the best way to get this info. I think with the search API you can still expand the dispute field on the charge object, so you may only need to make one API call here
rough badge
The documentation only shows a disputed field which is a Boolean. No expandable dispute field, is this an error in the documentation?
regal geyser
Apologis, that might have just been me making an assumption. Checking in to that
Yeah you are right, I think you might actually have to request each of those disputes individually after getting them with that list call.
You could do the list all disputes endpoint and filter on each charge ID https://stripe.com/docs/api/disputes/list#list_disputes-charge
rough badge
Ok that's what I planned to do if there wasn't a simpler way, thank you for your help.