Trengo · Rate Limits
Trengo Rate Limits
The Trengo REST API enforces a per-token rate limit of 120 requests per minute. Requests that exceed the limit receive an HTTP 429 (Too Many Requests) response. Responses include a Retry-After header (seconds to wait) and an X-RateLimit-Reset header (when the next call is allowed); honoring Retry-After is the recommended way to back off.
Trengo Rate Limits is the machine-readable rate-limit profile for Trengo on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition, measuring requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Customer Engagement, Omnichannel, Shared Inbox, Messaging, and WhatsApp.
1 Limits
Throttle: 429
Customer EngagementOmnichannelShared InboxMessagingWhatsAppRate LimitingQuotasThrottling
Limits
Requests Per Minute (per token) token
120
120 requests per minute per personal access token across the v2 REST API.
Policies
Retry-After Header
On a 429, the Retry-After header gives the number of seconds to wait before retrying; this is the safest signal because it avoids clock-sync issues.
X-RateLimit-Reset Header
The X-RateLimit-Reset header indicates when the rate limit window resets and the next call becomes available.
Backoff Strategy
Clients should implement exponential backoff with jitter and respect Retry-After rather than retrying immediately.