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 3 rate-limit definitions, measuring requests and messages.

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

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

3 Limits Throttle: 429
SMSMMSMessagingMarketingText MessagingRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Per-account API request throttling; numeric values not published in the public reference.
Message Throughput (MPS) number
messages
see provider documentation
Outbound messages-per-second governed by sending number type (toll-free, 10DLC, short code) and carrier registration.
Webhook Delivery Rate webhook
requests
configurable via requestPerSecLimit
The requestPerSecLimit field on a webhook caps how fast SimpleTexting posts callback events to your endpoint.

Policies

Number-Based Throughput
Sending throughput depends on number type and 10DLC / toll-free registration status; registered campaigns receive higher throughput.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.

Sources