RingCentral · Rate Limits

Ringcentral Rate Limits

RingCentral applies per-user, per-application rate limits to every REST API call. Each operation is bucketed into one of four categories — Light, Medium, Heavy, or Auth — each with its own per-minute quota. Exceeding a quota returns HTTP 429 with a Retry-After header. Default per-app limits can be raised via the Developer Console for production-graded apps.

Ringcentral Rate Limits is the machine-readable rate-limit profile for RingCentral on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Communications, UCaaS, Voice, Video, and Contact Center.

4 Limits Throttle: 429
CommunicationsUCaaSVoiceVideoContact CenterRate LimitingQuotasThrottling

Limits

Light Category user-per-app
requests · minute
50
Read-mostly endpoints such as account lookups, fetching extensions, and reading message metadata.
Medium Category user-per-app
requests · minute
40
Standard REST operations including most sends, updates, and listings.
Heavy Category user-per-app
requests · minute
10
Expensive operations such as bulk messaging, fax sends, large reporting/analytics queries, and recording downloads.
Authentication Category user-per-app
requests · minute
5
Token issuance, refresh, and revocation endpoints (/restapi/oauth/*).

Policies

Backoff Strategy
Clients must implement exponential backoff with jitter and honor the Retry-After header. Apps should also respect category-specific quotas by inspecting the X-Rate-Limit-* headers returned on every response.
App Graduation
Apps in sandbox have lower defaults than production. After graduation through the Developer Console, an app receives the standard production quotas above; further increases are negotiated with RingCentral.

Sources