In this section, you'll find all the conventional HTTP error codes associated with Xoxoday's Reward APIs.
Xoxoday Plum Pro API uses conventional HTTP status codes to indicate success or failure. Responses with a status code starting with 4xx or 5xx can be considered as failed. The API returns errors in JS
Error Code Definitions
Different attributes associated with the error codes and objects are defined below:
Attributes | Description |
---|---|
code | The HTTP status code of error returned. Can be: 2xx, 4xx, 5xx |
key | A short string from the list on the right-hand side describes the kind of error which occurred. |
message | Message providing a short description of the error |
details | Message providing more details about the error |
Standard HTTP status code summary
Below is the standard HTTP error code summary:
HTTP Status Code | Text | Description |
---|---|---|
400 | Bad request | The request was invalid, This happens mainly because of a malformed JSON or a violated rule |
401 | Unauthorized | Authorization failed or not provided yet |
404 | Not Found | The requested resource could not be found |
405 | Method Not Allowed | The request method is known by the server but has been disabled and cannot be used. The two mandatory methods, GET and HEAD , must never be disabled and should not return this error code. |
406 | Not Acceptable | This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content that conforms to the criteria given by the user agent. |
415 | Unsupported Media Type | The media format of the requested data is not supported by the server, so the server is rejecting the request. |
500 | Internal Server Error | This happens because of an internal server error, reach out to the [email protected] to get an immediate resolution. |
HTTP Code Meaning
All other HTTP code returned by the service has conventional meanings.
Please refer to the meaning of HTTP codes here -> https://developer.mozilla.org/en-US/docs/Web/HTTP/Status