Tyntec Rate Limits
tyntec does not publish fixed numeric per-second request limits for its public REST APIs in the general reference. Throughput on the messaging surfaces (SMS and Conversations) is governed primarily by carrier and channel constraints - A2P SMS throughput allocated to your account and, for WhatsApp, the messaging limits and quality rating that Meta assigns to your WhatsApp Business phone number. Number verification and HLR lookups are metered per transaction against account balance rather than a documented per-minute cap. Clients should handle 429 responses with backoff.
Tyntec Rate Limits is the machine-readable rate-limit profile for tyntec on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests, messages, unique_recipients, and lookups.
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 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include CPaaS, SMS, WhatsApp, Number Verification, and Rate Limiting.
generated, dated 2026-07-11.
Limits
Policies
Sources
- https://api.tyntec.com/reference/
- https://api.tyntec.com/reference/conversations/current.html
- https://www.tyntec.com/helpcenter/docs/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.