#todordvv_api

1 messages ¡ Page 1 of 1 (latest)

jovial domeBOT
#

👋 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/1372577769946484827

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

crisp robin
#

Here's is how the date is clearly visible on the dashboard payment page:

sand lintel
#

Hello there

#

We don't record "updated" as a property in our API, but it sounds like what you actually care about is the disputed date?

crisp robin
#

the dispute resolution date to be precise

#

for the dispute there is a date created, then there's a date where evidence is being exchanged

#

but I can't find the date where the dispute ended in the API

#

specifically this dispute:

#

du_1R2YDDAfnOjkPCjdnH6PvyHV

#

I need to get Apr 4, 2025, 5:17 PM back as a date

#

but I can't find it in any API parameter

sand lintel
#

Gotcha, you want to use Webhooks for this and listen for charge.dispute.closed

#

The status of the dispute changes to lost at that point

crisp robin
#

Yeah I figured that's one option but can't we do it without webhooks?

sand lintel
#

No there is no timestamp in the API that is updated when the dispute is closed.

crisp robin
#

Okay so it wasn't just me not being able to find it, thanks for the clarification.

sand lintel
#

Yeah, unfortunately Webhooks would be the only way here.

crisp robin
#

yeah, unfortunately for this usecase it's not an option, since this is an "on demand" reporting tool we're building

#

that's getting data from API

#

we didn't build it with webhooks since the validity of the data needs to be undisputed, in any case that answers my question I guess I'll consult with the client about workarounds to this

#

we do have the evidence date and the date the dispute is created so guess we'll have to do something with that

sand lintel
#

You could set metadata at the time of the Webhook

#

Then retrieve that via the API later

#

But still requires Webhooks

crisp robin
#

Hmm that is actually not a bad idea, thanks!

#

Even if it fails to update the failure rate would probably be negligeable.

#

Thanks so much, you've given me an alternative at the least!

sand lintel
#

Happy to help

crisp robin
#

Oh one last silly idea question:

#

if we go about it the backwards way and get all events - it does say something about events not being available after 30 days

#

does this mean that we can't get older events via API or does it just mean that the returned data will be incomlpete?

sand lintel
#

Events are deleted after 30 days so they can't be retrieved via the API after that point.

crisp robin
#

Got it! Thanks!