Revert · Rate Limits

Revert Api Rate Limits

Revert does not publish fixed numeric rate limits for its unified API. The open-source backend applies a rate-limit middleware (rateLimitMiddleware) in front of the /crm, /chat, /ticket, /accounting, and /ats routers, so limits on a self-hosted deployment are whatever you configure. In practice the binding constraint is usually the downstream provider's own API limits (Salesforce, HubSpot, Slack, Jira, etc.), since Revert proxies and normalizes calls to those providers; Revert manages OAuth token refresh and retries failed calls on your behalf. On the (now-retired) hosted Revert Cloud, throughput was governed by plan connection allowances rather than a documented per-minute request cap.

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

It captures 4 rate-limit definitions, measuring requests and connections.

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

Tagged areas include Unified API, Integrations, Open Source, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Unified APIIntegrationsOpen SourceRate LimitingQuotas

Limits

Unified API Requests account
requests
not published
No fixed numeric request-rate limit is documented. Self-hosted deployments apply a configurable rate-limit middleware.
Self-Hosted Throughput deployment
requests
configurable
Bounded by your own infrastructure and the rate-limit middleware you configure.
Downstream Provider Limits connection
requests
provider-defined
Effective throughput per connection is capped by the underlying CRM/chat/ticketing provider's own API rate limits.
Cloud Connection Allowance account
connections
per plan (retired)
Historical Revert Cloud metered linked connections per plan tier rather than request rate. Hosted service retired.

Policies

Automatic Retries
Revert automatically retries failed downstream API calls to improve reliability.
Token Refresh
Revert transparently refreshes expired OAuth tokens for linked connections so calls do not fail on auth expiry.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses, especially when a downstream provider throttles.

Sources