/mcpClientLog API Parameters Notes Possible Values Description Type Parameter Maximum of 12 characters. The user must be configured in Unified CCE or Unified CCX. — The ID of the user. The ClientLog API uses the id in the name of the log file created on the Finesse server. String id Must not exceed 1,048,576 characters. The user must be authorized to perform the POST operation. — The log data that the client sends to the Finesse server to be stored as a log file. String logData ClientLog API Errors Description Error Type Status The logData parameter is not present. Parameter Missing 400 The size of the logData exceeds 1,048,576 characters. Invalid Input 400 The POST client log operation failed. Operation Failure 400 The user is not yet authenticated in the Web Session. Authorization Failure 401 The authenticated user tried to make a request for another user. Invalid Authorization User Specified 401 GET or PUT HTTP method not allowed for client-side log collection. Method Not Allowed 405 Task Routing APIs Task Routing APIs provide a standard way to request, queue, route, and handle third-party multichannel tasks in CCE. Contact Center customers or partners can develop applications using SocialMinerCustomer Collaboration Platform and Finesse APIs in order to use Task Routing. The SocialMinerCustomer Collaboration Platform Task API enables applications to submit nonvoice task requests to CCE. The Finesse APIs enable agents to sign into different types of media and handle the tasks. Agents sign into and manage their state in each media independently. Cisco partners can use the sample code available on Cisco DevNet as a guide for building these applications (https://developer.cisco.com/site/task-routing/). For Finesse, the APIs used for Task Routing include the Media APIs and some of the Dialog and User APIs. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 166 Cisco Finesse Desktop APIs ClientLog API Parameters