Return Codes
All methods are implemented in such a way that the response contains not only the information returned by the request in the corresponding cases, but the return code that indicates the result, successful or not, of the operation performed.
If the result of the operation is not successful, in addition to the corresponding return code, a collection is returned with all the errors of Deyel that have occurred.
Although each method implements its own return codes for its operation, all possible HTTP return codes are described in the following table.
HTTP response code |
Description |
|---|---|
200 |
“OK” success code, for GET or HEAD request. |
201 |
“Created” success code, for POST request. |
202 |
"Updated" success code, for PUT request. |
204 |
“No Content” success code, for DELETE request. |
400 |
The request couldn't be understood, usually because the JSON or XML body contains an error. |
401 |
The session ID or OAuth token used has expired or is invalid. The response body contains the message and errorCode. |
403 |
The request has been refused. Verify that the logged-in user has appropriate permissions. If the error code is REQUEST_LIMIT_EXCEEDED, you've exceeded API request limits in your org. |
404 |
The requested resource couldn't be found. Check the URI for errors, and verify that there are no sharing issues. |
405 |
The method specified in the Request-Line isn't allowed for the resource specified in the URI. |
415 |
The entity in the request is in a format that's not supported by the specified method. |
500 |
An error has occurred within Deyel Platform, so the request could not be completed. Contact Deyel Customer Support. |
503 |
Service unavailable. Contact Deyel Customer Support. |
