McDewey

202: Success This response only indicates the successful completion of the request. The request is processed and the actual response is sent as part of a User notification. 400: Invalid Input (for example, the mode provided is invalid) 400: Parameter Missing (for example the mode or dialNumber was not provided) 400: Generic Error 401: Unauthorized (for example, the user is not authenticated in the Web Session) 401: Invalid User Authorization Specified (an authenticated user tried to make a request for another user) 404: User Not Found (for example, the agent is not recognized) HTTP Response: <ApiErrors> <ApiError> <ErrorType>Invalid Authorization User Specified</ErrorType> <ErrorData>4321</ErrorData> <ErrorMessage>The user specified in the authentication credentials and the uri don't match</ErrorMessage> </ApiError> </ApiErrors> Example Failure Response: User notification Notifications Triggered: Asynchronous Errors When accessing the Finesse REST API through the Finesse JavaScript library, asynchronous errors have a status code of 400. When receiving the asynchronous error directly through XMPP, the error message has the format described in "Dialog CTI Error Notification." Note Deployment Type Reason ErrorType Unified CCE Attempt to sign in an agent as a mobile agent when that agent is not configured as a mobile agent. Mode Not Allowed User—Sign Out of Finesse Desktop This API allows a user to sign out of Cisco Finesse desktop. Administrators can use the CLI utils finesse user_signout_channel to configure the media channels from which the users are signed out. Note https://<FQDN>/finesse/api/User/<id> URI: https://finesse1.xyz.com/finesse/api/User/1234 Example URI: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 32 Cisco Finesse Desktop APIs User—Sign Out of Finesse Desktop