Chatwoot · Rate Limits

Chatwoot Com Rate Limits

Chatwoot does not publish fixed, product-wide API rate-limit numbers in its developer documentation. Because the platform is open-source and commonly self-hosted, effective limits depend on the deployment: Rack::Attack throttles and any reverse-proxy (nginx) or CDN limits configured by the operator on self-hosted installs, and Chatwoot Cloud's own infrastructure protections on the hosted service. Clients should treat limits as deployment-specific and handle HTTP 429 responses gracefully.

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

It captures 3 rate-limit definitions, measuring requests.

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

Tagged areas include Customer Support, Shared Inbox, Open Source, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Customer SupportShared InboxOpen SourceRate LimitingQuotasThrottling

Limits

Application API Requests account
requests
deployment-specific
Governed by Rack::Attack and any proxy/CDN limits on the installation; Cloud enforces its own infrastructure protections.
Client API Requests inbox
requests
deployment-specific
Public widget-facing endpoints; subject to the same deployment-level throttling and abuse protection.
Platform API Requests installation
requests
deployment-specific
Super-admin endpoints; typically low-volume administrative use, still subject to installation-level throttling.

Policies

Handle 429
Back off on HTTP 429 responses with exponential backoff and jitter, and honor any Retry-After header the deployment returns.
Self-Hosted Tuning
Operators can tune throttling via Rack::Attack and their reverse proxy (nginx) or CDN; there is no single fixed public limit to code against.

Sources