Termii · Rate Limits

Termii Rate Limits

Termii enforces account-level throughput controls on its messaging and token endpoints, including a per-request bulk recipient cap (up to 100 numbers per send, and up to 10,000 via the bulk SMS workflow) and provider-side delivery throttling that varies by sender ID approval, route (DND vs. generic), and destination network. Termii does not publish explicit numeric per-second or per-minute API request limits; specific values are not reconciled in this artifact.

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

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

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

Tagged areas include Messaging, SMS, OTP, WhatsApp, and Verification.

4 Limits Throttle: 429
MessagingSMSOTPWhatsAppVerificationRate LimitingQuotasThrottling

Limits

Recipients Per Send request
recipients
up to 100 per /sms/send and /sms/send/bulk request
The `to` array accepts up to 100 numbers per request.
Bulk Campaign Recipients request
recipients
up to 10,000 via bulk SMS workflow
Bulk SMS workflow supports sending to up to 10k numbers in one request.
API Requests account
requests
see provider documentation
Termii does not publish explicit numeric per-second/per-minute API limits.
Delivery Throttling account
messages
see provider documentation
Delivery rate varies by sender ID approval, route (DND/generic), and network.

Policies

Sender ID Approval
Higher and more reliable delivery throughput depends on approved sender IDs and registered use cases.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses.

Sources