8x8 API might return the following HTTP error codes:
| Code | Description |
|---|---|
| 200 | OK, The request has succeeded. |
| 201 | Created, The request has succeeded and a new resource has been created as a result. |
| 202 | Accepted, The request has been received but not yet acted upon. |
| 204 | No Content, The request has succeeded, but there is no content to send as a response. |
| 400 | Bad Request, Request has invalid syntax. |
| 401 | Unauthorized, The client must provide the correct API key in the Authorization header. |
| 403 | Forbidden, The client is authenticated but does not have permissions to the content |
| 404 | Not Found, The server can not find the requested resource. |
| 410 | Gone, The requested content has been permanently deleted from the server, with no forwarding address. This usually applied to the API version that's not supported anymore. |
| 422 | 422 Unprocessable Entity, The request was well-formed but was unable to be followed due to semantic errors. |
| 429 | Too Many Requests, The user has sent too many requests in a given amount of time ("rate limiting"). |
| 500 | Internal Server Error, The server has encountered a situation it doesn't know how to handle. |
All API responses with HTTP code 400 and above has the following properties:
code(integer) - Error codemessage(string) - Human-readable error descriptionerrorId(UUID) - Unique id of the error. You can use it as a reference when sending inquiries to 8x8 support.timestamp(string, date-time) - Date and time of the error occurrence. Format:yyyy-MM-ddTHH:mm:ss.ffZ
{
"code": 1300,
"message": "Object wasn't found or is already expired",
"errorId": "1cc1eda1-f5dd-ea11-8288-0263195dd35a",
"timestamp": "2020-12-22T05:52:01.85Z"
}