SimpleTexting · Rate Limits

Simpletexting Rate Limits

SimpleTexting's API enforces request throttling and message-sending throughput limits. Outbound message throughput (messages per second) is governed by the type and registration status of the sending number (toll-free, 10DLC local, or short code) and the associated carrier approval, rather than a single documented API quota. Webhooks accept a configurable requestPerSecLimit to cap callback delivery rate. Specific numeric request-per-second and per-minute API limits are not published in the public API reference and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring items per request, requests, and messages.

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

Tagged areas include SMS, MMS, Messaging, Marketing, and Text Messaging.

4 Limits Throttle: not documented
SMSMMSMessagingMarketingText MessagingRate LimitingQuotasThrottling

Limits

Page size endpoint
items per request
500
The only hard numeric limit SimpleTexting publishes for the API itself — the `size` query parameter on every list operation has maximum 500, default 50 (OpenAPI parameter schema).
Webhook delivery rate webhook subscription
requests
25
`requestPerSecLimit` on a webhook subscription, maximum 25 (OpenAPI WebhookRequest schema). This caps how fast SimpleTexting calls YOUR endpoint; it is not a limit on your calls to SimpleTexting.
API request rate account
requests
not published
No per-account or per-key request quota appears anywhere in the public reference, and no header exposes one at runtime.
Message throughput (MPS) sending number
messages
not published
Outbound throughput is governed by sending number type (toll-free, 10DLC local, short code) and carrier registration status rather than by an API quota. SimpleTexting publishes no numeric MPS figure per number type.

Policies

Number-Based Throughput
Sending throughput depends on number type and 10DLC / toll-free registration status; registered campaigns receive higher throughput.
Backoff Strategy
Because no limit, status code or Retry-After header is published, clients should apply conservative exponential backoff with jitter on any non-2xx and must NOT blind-retry message or campaign sends — the API has no idempotency key, so a retry can bill a second send (conventions/simpletexting-conventions.yml).

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/simpletexting-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.