SMSAPI · Rate Limits

Smsapi Rate Limits

SMSAPI enforces a per-IP request rate limit on the HTTP API (documented at roughly 100 requests per second per IP) and requires TLS 1.2. Beyond raw request throughput, effective send throughput is governed by the prepaid credit balance and, for high-volume traffic, by operator- and route-level throughput agreements. Bulk sends should be batched (many recipients per /sms.do call) rather than issued as one request per recipient. Specific per-account throughput values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests, recipients, messages, and protocol.

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

Tagged areas include Messaging, SMS, MMS, Voice, and Rate Limiting.

4 Limits Throttle: 429
MessagingSMSMMSVoiceRate LimitingQuotasThrottling

Limits

Requests Per Second (per IP) ip
requests
100
Documented ceiling of ~100 requests/second per source IP on the HTTP API.
Recipients Per Request request
recipients
batch many recipients per call
Use the "to" parameter with multiple comma-separated numbers instead of one request per recipient.
Account Send Throughput account
messages
see provider documentation
Effective throughput depends on prepaid balance and operator/route agreements; varies by account.
TLS Requirement transport
protocol
TLS 1.2 minimum
Requests must use TLS 1.2 or higher.

Policies

Batching
Send to many recipients in a single request to stay within request-rate limits and reduce overhead.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.
Failover Host
A secondary host (api2.smsapi.com) is available for redundancy if the primary host is unreachable.

Sources