#_mark_simpson_
wind fjord
frozen pawn
hello, yeah AFAIK no other timestamps, you can listen (or fetch) the charge.dispute.updated and infer from the Event's created timestamp: https://stripe.com/docs/api/events/types#event_types-charge.dispute.updated
cursive solar
So not from the dispute itself but by fetching dispute events, i could piece together the info about when it was resolved? (I am saying fetch the events rather than listen for, as I am likely building a periodic job to gather info rather than something that must be kept up to date second-to-second...)
frozen pawn
yep you have that exactly right! (better worded than even what I said) 😃
one caveat is that Events are only retained for 30 days
so if you did the webhooks approach, and stored every created timestamp in a db on your end, then you have all historical records
Events fetched from the API are only retained from the past 30 days
We only guarantee access to events through the Retrieve Event API for 30 days.
https://stripe.com/docs/api/events
let me know if you have more questions
cursive solar
I did see that 30 day caveat... I'll need to be careful about that one. Thanks for your help!