HTTP return codes

When you submit a request using Web services, HTTP provides these messages that you can use to help determine if your request was processed correctly.

Ricoh ProcessDirector Web services support these HTTP return codes:

200 OK

The request has been processed with no errors.

202 Accepted

The request has been accepted for processing, but the processing has not been completed. There is no facility for resending a status code from an asynchronous operation such as this.

206 Partial Content

Some elements of the request were processed successfully. Messages in the response body indicate the portions that were not successful. If all elements of a multi-ID request succeed, a return code 200 results; if all fail, a return code 500 should result.

400 Bad Request

The request contains incorrect data or invalid syntax and cannot be processed. Resubmitting the request does not solve this problem.

401 Unauthorized

No credentials were supplied, or the supplied credential does not permit access to the requested service.

404 Not Found

The request included an object that did not exist at the time of the request.

409 Conflict

The request data given conflicts with itself or with the current state of the resource.

500 Internal Server Error

The server encountered an unexpected condition that prevented it from filling the request. This return code is expected to be the most common (or general) failure code. Details should be contained in a message element or elements in the entity-body.

501 Not Implemented

The resource does not support the request. Resubmitting the request does not solve this problem.

503 Service Unavailable

The Web service cannot complete the request because of a communication failure. Resubmitting the request might solve the problem.
 
Copyright © 2015, 2018