/mcpNo 500 The content type is only validated to ensure it does not exceed the maximum length. You must make sure you provide a valid content type. If the parameter is empty, no content type header is sent with the HTTP_REQUEST. The value of the content type header to send with the HTTP_REQUEST contentType No 2000 A free form text string that is included in the body of the request. It may be JSON, XPATH or any other format. It is not validated. If xml is included in the value it must be well formed xml. Variables may be embedded into the body by using a dollar sign curly braces. For example: <foo>${callVariable1}</foo> causes the workflow engine to substitute the value of callVariable1 into the body. If a literal curly brace or dollar sign is needed in the body it must be escaped with a backslash: { A literal backslash must be escaped with another backslash : \ The body to send with the HTTP_REQUEST body WorkflowAction API Errors Description Error Type Status The request body is invalid. Bad Request 400 API error such as the object is stale or does not exist. Finesse API Error 400 Unauthorized (for example, the user is not yet authenticated in the Web Session). The user is not authorized to use the API (the user is not an administrator). Authorization Failure 401 The user attempted to run the API against the secondary Finesse server. Configuration APIs cannot be run against the secondary Finesse server. Forbidden 403 The specified resource cannot be found. Not Found 404 Any runtime exception is caught and responded with this error. Internal Server Error 500 Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 314 Cisco Finesse Configuration APIs WorkflowAction API Errors