specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Termii
providerId: termii
created: '2026-06-20'
modified: '2026-06-20'
reconciled: false
tags:
- Messaging
- SMS
- OTP
- WhatsApp
- Verification
- Rate Limiting
- Quotas
- Throttling
description: >-
  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.
notes: >-
  Verify current request and delivery throttling, bulk recipient caps, and any
  per-second API limits in the Termii dashboard or with an account manager
  during reconciliation. Wallet balance also acts as a practical send ceiling.
sources:
- https://developers.termii.com/
- https://developers.termii.com/messaging-api
- https://blog.termii.com/termii-bulk-sms-api-send-sms-to-up-to-10k-phone-numbers-with-a-single-api-request
responseCodes:
  throttled: 429
limits:
- name: Recipients Per Send
  scope: request
  metric: recipients
  limit: up to 100 per /sms/send and /sms/send/bulk request
  notes: The `to` array accepts up to 100 numbers per request.
- name: Bulk Campaign Recipients
  scope: request
  metric: recipients
  limit: up to 10,000 via bulk SMS workflow
  notes: Bulk SMS workflow supports sending to up to 10k numbers in one request.
- name: API Requests
  scope: account
  metric: requests
  limit: see provider documentation
  notes: Termii does not publish explicit numeric per-second/per-minute API limits.
- name: Delivery Throttling
  scope: account
  metric: messages
  limit: see provider documentation
  notes: Delivery rate varies by sender ID approval, route (DND/generic), and network.
policies:
- name: Sender ID Approval
  description: Higher and more reliable delivery throughput depends on approved sender IDs and registered use cases.
- name: Backoff Strategy
  description: Clients should implement exponential backoff with jitter and honor 429 responses.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com