Messente · Rate Limits

Messente Rate Limits

Messente applies fair-use throttling to its REST API to protect delivery quality and downstream carriers. Sustained request throughput and messaging send rate (messages per second) are governed per account and can be raised for high-volume senders on request. Bulk sending is designed to be submitted via the bulk Omnimessage endpoint rather than many concurrent single-message calls. Specific numeric limits are not published as fixed public values and are set per account.

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

It captures 3 rate-limit definitions, measuring requests, messages_per_second, and recipients.

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

Tagged areas include CPaaS, Messaging, SMS, Rate Limiting, and Quotas.

3 Limits Throttle: 429
CPaaSMessagingSMSRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Fair-use request throughput per account across all endpoints.
Messaging Throughput account
messages_per_second
see provider documentation
Send rate per account; raised for high-volume senders on request.
Bulk Omnimessage account
recipients
submit large sends via POST /omnimessages
Use the bulk endpoint for many recipients instead of concurrent single sends.

Policies

Fair Use
Throughput is governed per account to protect delivery quality and carrier relationships.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses.
High-Volume Onboarding
Contact Messente to raise send-rate limits and provision dedicated routes for high-volume traffic.

Sources