Jump to: navigation, search
(Sample)
 
(2 intermediate revisions by the same user not shown)
Line 23: Line 23:
  
 
==Sample==
 
==Sample==
The request involves sending a JSON body as well as adhering to the url path listed above.
+
The request involves sending a JSON body as well as adhering to the URL path listed above.
  
 
===Request===
 
===Request===
Line 36: Line 36:
  
 
===Response===
 
===Response===
The response consists of an HTTP response and a CometD response. For details on the JSON body result, please refer to the Workbin Resource reference.
+
The response consists of an HTTP response and a CometD response.
  
 
'''HTTP response'''
 
'''HTTP response'''
Line 47: Line 47:
 
</pre>
 
</pre>
  
'''CometD Responses'''
+
'''CometD Response'''
 
<pre>
 
<pre>
  
Line 65: Line 65:
 
</pre>
 
</pre>
  
 
[[Category:V:HTCC:8.5.2DRAFT]]
 
  
 
[[Category:V:HTCC:8.5.2DRAFT]]
 
[[Category:V:HTCC:8.5.2DRAFT]]

Latest revision as of 09:45, November 30, 2017

RequestStats

This operation is part of the Workbins API section of the Web Services API.

Overview

Agents can request statistics for a workbin.

Request URL /api/v2/workbins/{id}
HTTP Method POST
Required Features api-multimedia

Parameters

operationName RequestStats

Sample

The request involves sending a JSON body as well as adhering to the URL path listed above.

Request

POST api/v2/workbins/6c715fa9-de16-4d23-b07c-cbcb1caf3e07
{
    "operationName": "RequestStats"
}


Response

The response consists of an HTTP response and a CometD response.

HTTP response

 {
    "statusCode": 0,
    "referenceId": 7
 }

CometD Response


 {  
    "workbinStats":{  
       "abc2ad1b26ea4e9b8dd907eabe1672e4":{  
          "MaxMovedToQueueAt":"2017-09-12T18:05:40Z",
          "MinMovedToQueueAt":"2017-09-12T18:05:40Z",
          "NumberOfInteractions":1
       }
    },
    "id":"6c715fa9-de16-4d23-b07c-cbcb1caf3e07",
    "workbinType":"Agent",
    "messageType": "WorkbinStatsMessage",
    "referenceId": 7
 }
This page was last edited on November 30, 2017, at 09:45.
Comments or questions about this documentation? Contact us for support!