To ensure reliable and consistent delivery, seven uses a message throughput limit. This defines how many messages per second an account can send – regardless of the channel (SMS, RCS, WhatsApp, Viber, etc.).
Default Limit
The default throughput limit is 10 messages per second. This limit applies to all accounts unless otherwise agreed.
Why is there a throughput limit?
Ensures system stability
Prevents overload and temporary blocking by destination networks
Enables even distribution during large campaigns
Avoids sudden traffic spikes
Allows predictable and reproducible delivery times
What happens when the limit is exceeded?
If more messages are submitted than the limit allows:
additional messages are automatically placed in a queue
the queue is processed at the maximum allowed speed
no error occurs as long as the API requests are valid
Important: For very large volumes, the overall delivery time will increase accordingly.
Custom Limits
Higher throughput rates can be configured upon request.
To review such requests, we require:
account ID or the email associated with the account
planned messages per second or total message volume
target regions and timeframe
API Notes
The throughput limit affects message delivery, not the frequency of API requests.
You may send more API requests per second, but delivery will be smoothed internally to match the configured limit.
Examples
Example 1: Sending 1000 messages
Limit: 10 messages per second
→ minimum delivery time of 100 seconds
→ API requests may be faster; excess messages are queued automatically.
Example 2: Planning to send 50 messages per second
Default limit: 10 messages per second
→ 40 messages per second are queued
→ delivery proceeds steadily at 10 messages per second
Summary
Default limit: 10 messages per second
Excess messages are automatically queued
API request rate is not limited
Higher limits possible upon request
If you have questions, our support team will be happy to assist you.