This document discusses server errors that can occur in the RingCentral application programming interface (API). Server errors have an HTTP status code in the 50x range and can be difficult to diagnose without access to server logs. Common causes include high traffic or maintenance. If the error persists, the RingCentral developer support team can investigate server logs to resolve the issue.

1. Anirban Sen Chowdhary
Overview on RingCentral errors Part 2

2. In the last discussion here, we have seen different set of errors which
occurs in RingCentral application. The RingCentral API uses specific
error codes to make error processing for client applications more
simple and effective.

3. As already discussed in the last part, RingCentral application throws lot
of errors which is categorized and are listed below:
• Server Error - HTTP status codes caused by server. HTTP code from
50x.
• Authentication Error - HTTP status codes which shows authentication
issue : 40x
• Rate Limiting Error - HTTP status codes that comes into picture when
API call exceed defined Rate limit eg: 429

4. In this part we will discuss and look into Server Error in details.
The server returns HTTP response mainly of the 50x status code due to
some unexpected issues on the server side.

6. Well, server errors are actually very hard to analyze and detect and if
we don't have the access of the server or logs, it will be almost
impossible to know the root causes as the server could not be more
specific on what the exact problem is.

7. Sometimes servers are intentionally unavailable for maintenance
purpose which is a temporary state. Even high traffic and services not
accessible for that time can cause these issues.

8. We can only fix the error if we have a good access on the server and
the logs. Also with some debugging tools, we can analyze the problem.
Sometimes, clearing the browser cache is also suggested.
All we need is to wait for a little while and try again. Sometimes issues
get automatically resolved after 15 to 20 seconds of time.

9. We can also contact RingCentral Dev support team if problem persists
for a long time so that they can investigate the server log and resolve
the issue.

10. Few examples are:

11. As we see here, RingCentral APIs sometimes provides description
under Error Codes header and we can see in the API response.
In the next bslideslog we will discuss some other error types in details.