Hey RingCentral,
We're seeing some different behavior in the Glip Archive API today.
The archive data structure used to look like this:
{
"uri": "https://platform.ringcentral.com/restapi/v1.0/glip/data-export/.....",
"id": ".....",
"creationTime": "2019-05-03T00:02:04Z",
"lastModifiedTime": "2019-05-03T00:02:05Z",
"status": "Completed",
"result": [
{
"size": 1018,
"uri": "https://media.ringcentral.com/restapi/v1.0/glip/data-export/...../archive/1"
}
]
}Now it looks like this:
{
"uri": "https://platform.ringcentral.com/restapi/v1.0/glip/data-export/.....",
"id": ".....",
"creationTime": "2020-01-15T05:09:02Z",
"lastModifiedTime": "2020-01-15T05:09:06Z",
"status": "Completed",
"creator": {
"id": "....",
"firstName": "...",
"lastName": "..."
},
"specific": {
"timeFrom": "2020-01-13T00:00:00Z",
"timeTo": "2020-01-15T05:09:02Z"
},
"datasets": [
{
"id": "1",
"size": 271709,
"uri": "https://media.ringcentral.com/restapi/v1.0/glip/data-export/...../archive/1"
}
]
}The list of archive files is now in a field called `datasets` and the timeFrom date has been backdated a day to a midnight UTC value.
What's up? Was notification of this change made to the developer community?
