Request rate exceeded when sending sms

Question

question

Nirmal Babu asked Apr 28, '22 Nirmal Babu commented May 4, '22

Request rate exceeded when sending sms

Please find the error response below:

 HTTP Response
 =============    
 status code: 429
 server: nginx
 Date: Wed, 27 Apr 2022 17:17:34 GMT
 Content-Type: application/json;charset=utf-8
 Content-Length: 161
 Connection: keep-alive
 RCRequestId: edfe64b6-c64d-11ec-995d-0050568d1600
 RoutingKey: IAD01P18PAS04
 Retry-After: 2
 Content-Language: en-US
 X-Rate-Limit-Group: sms
 X-Rate-Limit-Limit: 60
 X-Rate-Limit-Remaining: 53
 X-Rate-Limit-Window: 60
    
 {
   \"errorCode\" : \"MSG-305\",
   \"message\" : \"Request rate exceeded\",
   \"errors\" : [ {
     \"errorCode\" : \"MSG-305\",
     \"message\" : \"Request rate exceeded\"
   } ]
 }
    
 HTTP Request
 ============
 HTTP POST https://platform.ringcentral.com/restapi/v1.0/account/~/extension/~/sms

Can you please help us in finding the root cause?

errors sending sms

1

1 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Byrne Reese ♦♦ commented · Apr 28, 2022 at 08:46 PM

I posted an answer below, but a colleague of mine followed up with me to let me know that he observed some irregularities in your example above, so we are investigating further.

0 ·

Using the RingCentral Phone for Desktop, you can dial or receive test calls, send and receive test SMS or Fax messages in your sandbox environment.

Download RingCentral Phone for Desktop:

Tip: switch to the "sandbox mode" before logging in the app:

On MacOS: press "fn + command + f2" keys
On Windows: press "Ctrl + F2" keys

Answer 1 · 2022-04-29T00:24:25Z

Phong Vu answered Apr 29, '22 Nirmal Babu commented May 4, '22

Since the /sms endpoint rate limit group is Medium, meaning 40 API calls (40 messages) per 60 seconds. You should call the endpoint following the Medium rate limit. The best approach is to send a message every 1.5 secs (DO NOT calling as fast as possible then wait for the next window)

Please read this article and use the 2 option (Call and wait based on the average rate limit)

The header returns a special sms group which may not be applied to your app and we are investigate this.

3

1 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Nirmal Babu commented · May 04, 2022 at 09:06 AM

From the error, we can see that the rate limit is not exceeded but why did it say 'Rate limit exceeded'? X-Rate-Limit-Limit: 60 X-Rate-Limit-Remaining: 53 Usually, when the rate limit is exceeded, we see the X-Rate-Limit-Remaining value to be 0. But that is not the case here. I guess you are investigating the same, any update on this?

0 ·

Phong Vu ♦♦ Nirmal Babu commented · May 04, 2022 at 02:28 PM

Recently, we made some change to have a special sms rate limit, which shown the group name as "sms" and the rate limit at 60 as you can see. However, the /sms endpoint is actually does not use that rate limit group, but rather in the Medium group as stated in the API reference documentation.

We are going to fix this in the future. But for now you should not use the value from the rate limit headers for the /sms endpoint.

1 ·

Nirmal Babu Phong Vu ♦♦ commented · May 04, 2022 at 03:42 PM

Sure Phong, Thanks for the update!

0 ·

Answer 2 · 2022-04-28T18:03:36Z

Byrne Reese answered Apr 28, '22

@Nirmal Babu This response is actually coming from our API gateway which helps us manage the throughput of any given operation or endpoint. Your application is being "throttled" meaning it is sending too many requests within a given time window. The error will go away in time. To learn more about throttling and rate limits, go here:

https://developers.ringcentral.com/guide/basics/rate-limits

Does this answer your question?

1 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

question