Rate Limits

Information on rate limits

An API rate limit restricts the number of requests a client can make to an API within a given period of time.

General Rate Limit

Most Mobile Text Alerts API endpoints have a general rate limit of 30 requests per minute per IP address. However, some individual endpoints may override the general rate limit (see below).

Rate limits are not the same as message throughput, which is measured in message segments per second (MPS). MPS throughput is determined based on the sender's brand type, campaign type (use case), and trust score (for Standard Brands).

Your rate limit usage can be tracked in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers.

Account-based rate limiting

Some endpoints use account-based rate limiting, where the rate limit is determined by the authenticated account instead of the IP address.

Endpoint	Rate Limit
POST /send	25 requests every 15 seconds
POST /groups/{groupId}/subscribers/bulk-create	5 requests every 15 seconds. A maximum of 1,000 records in a single request.
POST /groups/{groupId}/subscribers/bulk-delete	5 requests every 15 seconds. A maximum of 1,000 records in a single request.
GET /custom-fields	15 requests every 15 seconds
GET, POST /account-variables	15 requests every 15 seconds
GET, PATCH, DELETE /account-variables/{idOrTitle}	15 requests every 15 seconds
GET, POST /subscribers	15 requests every 15 seconds. For large scale subscriber changes Bulk Create/Update Subscribers endpoints are recommended.
GET, PATCH, DELETE /subscribers/:idOrNumber	15 requests every 15 seconds
POST, PATCH /subscribers/bulk	15 requests every 15 seconds. A maximum of 1,000 records in a single request.