McDewey

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

Page 69

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

The ReasonCode list can be empty (for example, if no reason codes for the specified category exist in the Finesse configuration database). Reason codes that have the forAll parameter set to true apply to any user. The category parameter is required when making a request to get a list of reason codes. For information about the ReasonCode object, see section on ReasonCode. Note https://<FQDN>/finesse/api/User/<id>/ReasonCodes?category=NOT_READY|LOGOUT URI: https://finesse1.xyz.com/finesse/api/User/1234/ReasonCodes?category=NOT_READY Example URI: Administrators, agents and supervisors can use this API. To get a list of reason codes, a user must be signed in or provide valid authorization credentials when challenged. Only an administrator can get another user's list of reason codes. Security Constraints: GET HTTP Method: — Content Type: XML Input/Output Format: — HTTP Request: 200: Success 400: Bad Request 400: Finesse API Error (for example, the object does not exist, the object is stale, or violation of DB constraint) 401: Authorization Failure 401: Invalid Authorization User Specified 404: Not Found 500: Internal Server Error HTTP Response: <ReasonCodes category="NOT_READY"> <ReasonCode> <uri>/finesse/api/ReasonCode/1</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: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 53 Cisco Finesse Desktop APIs User—Get Reason Code List

Image 1 from page 69