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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-01.
Written by API Evangelist on 2026-07-01 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/smsapi-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.