McDewey

C H A P T E R 5 Cisco Unity Connection Provisioning Interface (CUPI) API -- Error Handling Links to Other API pages: Cisco_Unity_Connection_APIs • Possible Errors, on page 11 Possible Errors The HTTP status codes themselves provide information about many typical errors. See the following list for some of the status codes returned by CUPI: Explanation Possible Errors Normal response when a page has been successfully fetched. 200 OK The resource has been created. 201 Created The page has moved permanently. It is usually a response from implementing a 301 redirect. 301 Moved Permanently The page has moved temporarily. 302 Moved Temporarily The request could not be understood by the server, due to incorrect syntax. 400 Bad Request Authentication is required. 401 Unauthorized User The server understood the request, but is refusing to fulfill it. 403 Forbidden The server has not found anything that matches the Request-URI. 404 Page Not Found The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. 405 Method Not Allowed The server cannot generate a response that the requester is willing to accept. 406 Not Acceptable The requested resource is no longer available at the server, and no forwarding address is known. This condition is similar to 404, except that the 410 error condition is expected to be permanent. 410 Gone The server is refusing the request, because the request is in a format not supported by the requested resource for the requested method. 415 Unsupported Media Type There is an internal web server error. 500 Server Error Cisco Unity Connection Provisioning Interface (CUPI) API 11