/mcp— HTTP Request: 200: Success 400: Bad Request (the request body is invalid) 400: Finesse API Error (for example, the object does not exist, the object is stale, or violation of the DB constraint) 401: Authorization Failure 401: Invalid Authorization 404: Not Found (for example, the teamId does not exist or has been deleted) 500: Internal Server Error HTTP Response: <ReasonCodes category="NOT_READY"> <ReasonCode> <uri>/finesse/api/ReasonCode/1234</uri> <category>NOT_READY</category> <code>12</code> <label>Lunch</label> <forAll>true</forAll> </ReasonCode> <ReasonCode> ...Full ReasonCode Object... </ReasonCode> <ReasonCode> ...Full ReasonCode Object... </ReasonCode> </ReasonCodes> Example Response: <ApiErrors> <ApiError> <ErrorType>Authorization Failure</ErrorType> <ErrorMessage>UNAUTHORIZED</ErrorMessage> <ErrorData>1234</ErrorData> </ApiError> </ApiErrors> Example Failure Response: TeamResource—Get Wrap-Up Reasons This API allows an agent or supervisor to get all the wrap-up reasons for a team. For more information about the WrapUpReason object, see WrapUpReason, on page 244. https://<FQDN>/finesse/api/TeamResource/<teamId>/WrapUpReasons URI: https://finesse1.xyz.com/finesse/api/TeamResource/1234/WrapUpReasons Example URI: Agents and supervisors who are part of the team can use this API. To get the wrap-up reason for the team, the user must be signed in or provide valid authorization credentials. Security Constraints: GET HTTP Method: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 152 Cisco Finesse Desktop APIs TeamResource—Get Wrap-Up Reasons