#daniel-archer_api

1 messages ¡ Page 1 of 1 (latest)

serene fogBOT
#

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

📝 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.

molten remnant
#

Hi there, sorry for the delay

celest bear
#

Hey thanks for helping me

molten remnant
#

Looks like either one should work ("YYYY-MM-DD", and as "MM-DD-YYYY"); we're just expecting a string that can be readable by a human (which is likely why we don't expect this to be a unix timestamp, for example)

celest bear
#

Hmm for some reason, any time I try updating this via the API, it doesn't save on to the record.

#

But if I update it from the Dashboard, I can see that it comes back in the API as YYYY-MM-DD

molten remnant
celest bear
#

Oh I see - it did come back in the response. When I look at the dispute in the dashboard, it's not showing the date in the UI.

molten remnant
#

I'm not sure if we'd show this shipping date value in the Dashboard at all. I see the Dashboard shows that evidence was submitted, and you can take a look at the Events in the Dispute view to see the values you passed via the API