Revert · Rate Limits

Revert Dev Rate Limits

Revert brokers calls to many downstream third-party providers, so effective throughput is bounded by two layers: Revert's own hosted API limits and the rate limits of each connected provider (Salesforce, HubSpot, Zoho, Pipedrive, Close, etc.). Revert normalizes provider throttling responses. When self-hosting (AGPL-3.0), Revert-side limits are whatever you configure on your own deployment; only the downstream provider limits apply. Specific hosted numeric limits are not published and are not reconciled in this artifact.

Revert Dev 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 3 rate-limit definitions, measuring requests.

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

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

3 Limits Throttle: 429
Unified APIIntegrationsCRMRate LimitingQuotasThrottling

Limits

Revert Hosted API Requests account
requests
see provider documentation
Hosted-plan request limits; not published, tier-dependent. Not applicable to self-hosted deployments.
Downstream Provider Limits connection
requests
varies by connected provider
Each connected CRM (Salesforce, HubSpot, Zoho, Pipedrive, Close, etc.) enforces its own rate limits, which pass through Revert.
Proxy Passthrough connection
requests
bounded by downstream provider
Proxy calls are subject to the underlying provider's native rate limits.

Policies

Provider Throttling Passthrough
When a downstream provider returns 429, Revert surfaces the throttle to the caller.
Automatic Retry
Revert includes an API retry mechanism that automatically retries certain failed downstream calls.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources