#nemtecl_webhooks

1 messages · Page 1 of 1 (latest)

brisk islandBOT
#

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

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

full wharf
#

hi! just to be sure I understand, what do you mean by "refuted"? That's not terminology I think we use in the API/docs for disputes

clever kernel
#

Oh my bad, probably bad translation on my side, it's "challenged"

full wharf
#

as in, you submitted evidence for the dispute?

clever kernel
#

Yes

In my understanding when a dispute is open you have two choice : accept or challenge it.

I'd like to find a way to determine if a dispute was accepted or challenged when listening on charge.dispute.closed 🙏

full wharf
#

then yes I would say you could check if any of the fields within the evidence hash are present. Another, maybe better way is that whenever you submit evidence by calling the Update Dispute API to set evidence, you can also set metadata and add something in there that will tell you later that you challenged it.

clever kernel
#

Nice thank you so much !

Is "has_evidence": true reliable enough too ?

#

I mean, if you challenge a dispute you will have to add evidence right ?

full wharf
#

ah yeah, has_evidence works too

#

and yes 'challenge a dispute' == submit evidence

clever kernel
#

Perfect that’s what I needed !

#

Thank you so much