Skip to main content

We're a software company, currently converting our decades-old app (a full-office medical office management package; known today as an ERP [and CRM] package) (began development in the late 1980s..) to Java/CUBA platform. The new version of our app will need 2FA via SMS for user login, and as our phone service is RingCentral... it seems easy enough to implement this via the RC Java API.


I have it all working; it's very easy to work with (kudos to RC for that), except...the rate limits are exceedingly low! 40 texts per minute? Really?


We have clients in all 50 US states, and we will be self-hosting this new app via Docker containers with each client in their own Docker'ed world, for safety and HIPPA act compliance. Early in the morning, when people are getting into their offices, there's going to be dozens/hundreds of 2FA requests.


Surely mere hundreds of SMS sends wouldn't kill RC's infrastructure. Why are the limits so LOW?

There are a few things I want to mention here.

1. API rate limit is per user and per API.

2. Normal phone number with SMS capability is designed for P2P SMS. It is not likely every user would send 40 messages per minute. Though, based on special request with business justification, case by case we can increase the API rate limit for an app.

3. Using a normal phone number to send A2P SMS is against carriers’ rules and as a result, the number would be blocked by a mobile carrier once they detected.

4. The right way to send A2P SMS is to use a Toll-Free SMS number. More info about TF SMS

5. We are introducing a High Volume SMS API to be used with Toll-Free SMS numbers which is dedicated for A2P SMS and is capable of sending more than 3 messages per second with super high API rate limit. This API is still in beta stage and can be accessed via early access program. Fill out this form if you would like to have access.

Reply


Terms & ConditionsCookie settings