Paragon · Rate Limits

Paragon Api Rate Limits

Paragon does not publish fixed numeric rate limits for its Connect/SDK, Workflows, ActionKit, or Proxy APIs. In practice, effective throughput is governed by two things: the Connected-User-based capacity of your plan, and the rate limits of the underlying third-party providers that the Proxy API and ActionKit call on your behalf (for example, Salesforce, HubSpot, or Slack API limits). Because Paragon requests are made per Connected User with short-lived JWTs, quotas are effectively scoped to your project and its Connected Users rather than to a single global API key.

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

It captures 3 rate-limit definitions, measuring requests and connected_users.

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

Tagged areas include Embedded iPaaS, Integrations, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Embedded iPaaSIntegrationsRate LimitingQuotas

Limits

Paragon API Requests project
requests
not published
No fixed numeric request-rate limit is documented for Paragon's own Connect, Workflows, ActionKit, or Proxy APIs.
Connected User Capacity project
connected_users
per plan
Plan capacity scales on the number of Connected Users rather than a request-per-minute cap.
Downstream Provider Limits integration
requests
provider-defined
Proxy API and ActionKit calls are subject to the rate limits of the third-party provider being called, which Paragon passes through.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses from Paragon or from the underlying provider surfaced via the Proxy API.
Per-User Scoping
Requests are authenticated per Connected User with short-lived RS256 JWTs, so throttling is effectively scoped to the project and its Connected Users.

Sources