The date fields CreationDate and LastModifiedDate which are part of the response of the two requests mentioned in the question are documented as string (Date/Time in UTC format).
I'm pretty sure that a few days ago (at least on Fri 27/11/2020), the data type of these fields was long/int64 (UnixTime in milliseconds).
Can anybody confirm please that this has been changed?
And can anybody explain why such changes aren't communicated in advance?
Thank you!
Solved
Changes in Response of API Requests "List Mailing Lists" and "Get Contact in Mailing List"?
+8Best answer by LaurenK
Hi StephanB! The Public API should return all dates in ISO-8601 format: https://api.qualtrics.com/instructions/docs/Instructions/dates-and-times.md; however some APIs were not following this standard and were returning in the incorrect format. Our developers have since fixed this to the correct format. The team is working on a process to improve communication of breaking changes.
+13Hi StephanB! The Public API should return all dates in ISO-8601 format: https://api.qualtrics.com/instructions/docs/Instructions/dates-and-times.md; however some APIs were not following this standard and were returning in the incorrect format. Our developers have since fixed this to the correct format. The team is working on a process to improve communication of breaking changes.
+8Hi LaurenK, thank you for your reply which is highly appreciated. The link is a helpful one as well.
Unfortunately, your developers had changed it again. I was not amused on 11 Dec 2020: Since then, the API response of the two requests changed back. All error troubleshooting we did on 1 Dec 2020 after the initial change was not enough as we were running into an error again 😕.
The documentation at https://api.qualtrics.com/api-reference/reference/mailingLists.json/paths/~1directories~1%7BdirectoryId%7D~1mailinglists/get is again wrong, as it shows string date/time for this request but it returns Unix milliseonds as integer.
The documentation at https://api.qualtrics.com/api-reference/reference/mailingListContacts.json/paths/~1directories~1%7BdirectoryId%7D~1mailinglists~1%7BmailingListId%7D~1contacts~1%7BcontactId%7D/get is correct again as the request does return int64.
So, an improval of communication would be important. How should we automate any API processes if Qualtrics changes the API without any proactive information?! This is not acceptable imho. Thank you!
+13https://www.qualtrics.com/community/discussion/comment/33708#Comment_33708StephanB - I've relayed this feedback over to the team!
1 person likes this
Leave a Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.