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.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/trengo-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.