McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 262

↗ View in doc context
page
262
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::246

200: Success 401: Authorization Failure 401: Invalid Authorization User Specified 403: Forbidden 404: Not Found 500: Internal Server Error HTTP Response: <WrapUpReasons> <WrapUpReason> ... Full WrapUpReason Object ... </WrapUpReason> <WrapUpReason> ... Full WrapUpReason Object ... </WrapUpReason> <WrapUpReason> ... Full WrapUpReason Object ... </WrapUpReason> </WrapUpReasons> Example Response: <ApiErrors> <ApiError> <ErrorType>Authorization Failure</ErrorType> <ErrorMessage>UNAUTHORIZED</ErrorMessage> <ErrorData>jsmith</ErrorData> </ApiError> </ApiErrors> Example Failure Response: WrapUpReason—Create This API allows an administrator to create a new wrap-up reason. The administrator specifies the label and forAll attributes for the wrap-up reason. Cisco Finesse does not support the use of extended ASCII characters required for additional alphabets in the wrap-up reasons. You must use only ASCII characters in the 0-127 range. For example, if you add a wrap-up reason that contains the character à (ASCII 133), it does not appear correctly on the agent desktop. Note Finesse supports a maximum of 100 global wrap-up reasons and 100 non-global wrap-up reasons. for each category. The forAll parameter determines if a reason code is global (true) or non-global (false). If you provide two or more duplicate tags in the XML body for a POST operation, the value of the last duplicate tag is processed and all other duplicate tags are ignored. Note https://<FQDN>/finesse/api/WrapUpReason/ URI: https://finesse1.xyz.com/finesse/api/WrapUpReason/ Example URI: Only administrators can use this API. Security Constraints: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 246 Cisco Finesse Configuration APIs WrapUpReason—Create

Image 1 from page 262