/mcpPhoneBook API Errors Description Error Type Status API error such as the object is stale or does not exist. Finesse API Error 400 One of the input parameters exceeded constraints. Contacts could not be imported because the data was invalid. The file may be empty or may not contain any valid lines. If the ErrorData field contains no lines, there may not be data to import. The multipart mime message may have been improperly formatted or did not contain a file. The multipart mime message may have been improperly formatted or did not contain a file. In this case, the existing records are overwritten. Invalid Input 400 The phone book is assiged to a team. You cannot change a team phone book to a global phone book if it is use. You cannot delete a phone book if it is use. In Use 400 The maximum number of phone books or contacts has been exceeded. Maximum Exceeded 400 A required parameter was not present in the request. Parameter Missing 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 authenticated user tried to use the identity of another user. Invalid Authorization User Specified 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 Contact The Contact object represents a contact that can be assigned to a phone book. A phone book can contain up to 6000 contacts. Finesse supports a system-wide total of 50,000 contacts. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 280 Cisco Finesse Configuration APIs PhoneBook API Errors