News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Search
Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
ringcentral-csharp: Handling 429 Exception - Too Many Requests
Tags: sdk
Nov 16, 2015 at 11:16am   •   1 replies  •  0 likes
andrew-smedley

I'd like to know how best to handle the 429 Error when using the ringcentral-csharp SDK. When the HttpResponseMessage is returned with an error code outside of 200-299, the Response constructor throws an exception. The exception does not contain details of the status error nor the headers of the HttpResponseMessage. According to the documentation: https://developer.ringcentral.com/api-docs/latest/index.html#!#HttpStatusCodes.html 429 - Too Many Requests The number of requests is exceeded. It typically means that the client is throttled by the server due to too high request rate. Specific retry period in seconds may be specified in Retry-After response header I expected to check the status myself and detect the 429 error, inspect the response header and handle the delay before retrying. A cannot see a way to handle this error myself and read the header for Retry-After. At the moment, it look like I need to inspect the string of the error for specific text and then delay 60 seconds. Is there a better way to handle this issue? If the exception was not thrown, I believe that would solve this particular issue but I am unsure of the side effects that this would cause.

1 Answer
answered on Nov 16, 2015 at 1:26pm  
There are a few use-cases when a 429 HTTP response will be returned:
  1. If your app/integration exceeds 10 requests per second to our OAuth resource
  2. If your app/integration exceeds 10 requests per second to the Call Log resource
  3. If your app/integration exceeds 20 requests per minute to any other API resource
Additionally, if you're making too many requests per second (3 is the recommended maximum) you'll also receive the 429 response.

Make sure that you're not exceeding this basic API limits and you should be good. Let me know if you continue experiencing this issue.

 0



A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

PRODUCTS
RingEX
Message
Video
Phone
OPEN ECOSYSTEM
Developer Platform
APIs
Integrated Apps
App Gallery
Developer support
Games and rewards

RESOURCES
Resource center
Blog
Product Releases
Accessibility
QUICK LINKS
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us