McDewey

202: Successfully Accepted This response only indicates a successful completion of the request. The request is processed asynchronously and the state change is sent as part of and updated to the Dialog object. The response is in the BAResponse call variable, which contains the value sent to the CTI server for the reclassify action. No confirmation is returned, other than the value in the BAResponse. Note 400: Bad Request 400: Finesse API Error (for example, the object does not exist or is stale) 400: Parameter Missing 401: Authorization Failure 401: Invalid Authorization User Specified 404: Dialog Not Found 500: Internal Server Error HTTP Response: <ApiErrors> <ApiError> <ErrorType>Authorization Failure</ErrorType> <ErrorMessage>UNAUTHORIZED</ErrorMessage> <ErrorData>jsmith</ErrorData> </ApiError> </ApiErrors> Example Failure Response: Dialog 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 All Attempt to reclassify a dialog that is not generated by the outbound campaign. Generic error Dialog—Schedule or Cancel a Callback This API allows a user to schedule or cancel a callback. The dialog action UPDATE_SCHEDULED_CALLBACK is used to schedule or update a callback. The dialog action CANCEL_SCHEDULED_CALLBACK is used to cancel a previously scheduled callback. https://<FQDN>/finesse/api/Dialog/<dialogId> URI: https://finesse1.xyz.com/finesse/api/Dialog/54321 Example URI: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 112 Cisco Finesse Desktop APIs Dialog—Schedule or Cancel a Callback