tyntec · Rate Limits

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, conforming to the API Commons Rate Limits specification.

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

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.

4 Limits Throttle: 429
CPaaSSMSWhatsAppNumber VerificationRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented in the public API reference.
SMS Throughput account
messages
carrier / account allocated
A2P SMS send rate depends on the throughput allocated to your account and destination network.
WhatsApp Messaging Limit phone_number
unique_recipients
Meta-assigned tier
Meta sets the WhatsApp Business messaging tier and quality rating per phone number, not tyntec.
Number Verification / HLR Lookups account
lookups
metered per transaction
Billed per lookup against account balance; no documented per-minute cap.

Policies

Backoff Strategy
On HTTP 429, retry with exponential backoff and jitter.
Channel Compliance
WhatsApp and SMS traffic must comply with channel and carrier policy (opt-in, template approval for WhatsApp) or delivery is throttled or blocked.

Sources