Propel · Rate Limits
Propel Data Rate Limits
Propel governs throughput on its GraphQL API through per-Application concurrency and request limits, the compute size (Propeller) assigned to an Application, and plan-level query quotas. Specific numeric limits depend on plan and Propeller and are not consistently published, so they are not reconciled in this artifact.
Propel Data Rate Limits is the machine-readable rate-limit profile for Propel on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests and queries.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Analytics, GraphQL, Data Warehouse, Metrics, and Customer Facing Analytics.
4 Limits
Throttle: 429
AnalyticsGraphQLData WarehouseMetricsCustomer Facing AnalyticsRate LimitingQuotasThrottling
Limits
Concurrent Queries application
see provider documentation
Concurrency scales with the Application's assigned Propeller size.
Requests Per Second (RPS) application
see provider documentation
Per-Application request rate; varies by plan and Propeller.
Query Quota account
see provider documentation
Plan-level monthly query volume included in the tier.
OAuth2 Token Requests application
see provider documentation
Token endpoint issuance; cache and reuse Bearer tokens until expiry.
Policies
Tiered Limits
Throughput rises with paid plans and larger Propeller compute sizes assigned to Applications.
Backoff Strategy
Clients should cache access tokens, batch multiple GraphQL queries per request where possible, and implement exponential backoff with jitter on 429 responses.