McDewey

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

Page 335

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

200: Success 400: Bad Request 400: Finesse API Error 401: Authorization Failure 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> <ErrorData>500</ErrorData> <ErrorType>finesse.api.team.team_assignment_invalid_ team&</ErrorType> <ErrorMessage>HTTP Status code: 404 (Not Found) Api Error Type:finesse.api.team.team_assignment_ invalid_team Error Message: This is not a valid team</ErrorMessage> </ApiError> </ApiErrors> Example Failure Response: Team—Update List of Wrap-Up Reasons This API allows an administrator to assign or unassign a list of wrap-up reasons to a team. If multiple users try to update the wrap-up reasons for the same team at the same time, the changes made by the last user to update overwrite the changes made by the other users. This list includes all wrap-up reasons that are assigned to a team. Any wrap-up reasons that you assign or unassign overwrite the current wrap-up reason list. https://<FQDN>/finesse/api/Team/<Id>/WrapUpReasons URI: https://finesse1.xyz.com/finesse/api/Team/574/WrapUpReasons Example URI: Only administrators can use this API. Security Constraints: PUT HTTP Method: Application/XML Content Type: XML Input/Output Format: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 319 Cisco Finesse Configuration APIs Team—Update List of Wrap-Up Reasons