Queries Evaluations Endpoint /api/v2/quality/evaluations/query completion date not matching with Genesys UI

Platform API .NET SDK
1

Hi Team,

Queries Evaluations Endpoint /api/v2/quality/evaluations/query related timestamps not matching with completion date in Genesys UI.
We tried to use releaseDate, changedDate and revisionCreatedDate returned by the API. But none of the timestamps are matching with completed timestamp in Genesys UI.
Could someone dig into this issue

2

Did you account for the timestamps in the API being in UTC and the timestamps you see in the Genesys UI being local to whoever is looking at them?

3

The timezone related to Genesy UI is in UTC only.

4

Then you may need to open a customer care case to report and investigate the difference.

5

Hi Team,
Opened a case with Genesys and below is the response.
**

"api/v2/quality/evaluations/query" will not provide the exact submitted time, which is where the timestamps in our UI come from.

**

We should use "/api/v2/quality/conversations/{conversationId}/evaluations/{evaluationId}?expand=versionHistory" You can notate the "version" provided by the API in the response to get the order as well as using the "/api/v2/quality/conversations/{conversationId}/evaluations/{evaluationId}" API along with expanding version history to get the exact time each evaluation was submitted for the conversation

Below is the json response for "/api/v2/quality/conversations/{conversationId}/evaluations/{evaluationId}?expand=versionHistory"

"versionHistory": {

  "total": 2

  "entities": [

   {

    "id": "********",

    "submittedDate": "2024-01-03T16:50:41.948Z",

    "version": 2,

    "status": "FINISHED",

    "selfUri": "/api/v2/quality/conversations/{conversationId}/evaluations/{evaluationId}"

   },

   {

    "id": "********",

    "submittedDate": "2023-12-06T20:36:38.055Z",

    "version": 1,

    "status": "RETRACTED",

    "selfUri": "/api/v2/quality/conversations/{conversationId}/evaluations/{evaluationId}"

   }
]
}

So is there any other options or any workarounds to use Endpoint1 instead of Endpoint2