McDewey

200: Success 400: Bad Request 401: Invalid Supervisor 401: Unauthorized 404: Not Found 500: Internal Server Error 503: Service Unavailable HTTP Response: <ApiErrors> <ApiError> <ErrorType>Parameter Missing</ErrorType> <ErrorData>state</ErrorData> <ErrorMessage>State Parameter missing</ErrorMessage> </ApiError> </ApiErrors> Example Failure Response: User notification Notifications Triggered: Platform-Based API Differences The following table describes API differences between a stand-alone Finesse deployment with Unified CCE and a coresident Finesse deployment with Unified CCX. Response Scenario Stand-alone Finesse with Unified CCE: <data> <apiErrors> <apiError> <errorData>257</errorData> <errorMessage>CF_INVALID_PASSWORD_SPECIFIED</errorMessage> <errorType>Invalid State</errorType> </apiError> </apiErrors> </data> Coresident Finesse with Unified CCX: <data> <apiErrors> <apiError> <errorData>1010</errorData> <errorMessage>CF_INVALID_PARAMETER</errorMessage> <errorType>Invalid State</errorType> </apiError> </apiErrors> </data> Change from LOGOUT to NOT_READY. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 48 Cisco Finesse Desktop APIs User—Change Agent State