Player evidence report HTTP response#

The following code is an example of a player evidence response:

{
   "request_start_ts": 1706203970429807,
   "next": 1704400836045162,
   "conversations": [
       {
           "message_count": 2,
           "last_activity": 1704400939799491,
           "conversation_uri": "sip:confctl-g-your-issuer.test-channel-1@youvivoxdomainname.vivox.com"
       },
       {
           "message_count": 1,
           "last_activity": 1704400878101904,
           "conversation_uri": "sip:your-issuer.doe@yourvivoxdomainname.vivox.com"
       }
   ]
}

The next field is used for pagination and represents the player’s most recent activity in the next conversation returned. This value will be null if there are no more pages of results to return. Use the next value as the end_ts in a subsequent request to retrieve the next page of results. The request_start_ts is also used for pagination and represents the timestamp of the initial request. This value maintains consistency in paging results if the player is active during review. The request_start_ts is required when using the next value to request subsequent pages of results.

The conversation objects in the response contain the following fields:

• message_count: The number of messages sent to the conversation by the user.
• last_activity: The user’s last activity in the conversation.
• conversation_uri: The conversation identifier. This value can be used in Text Evidence report requests to view conversation messages.

Returned conversation results are in order of the player’s most recent activity.