Revenuecat Rate Limits
RevenueCat enforces per-endpoint rate limits expressed in requests per minute (RPM), scoped by the endpoint being called rather than by billing tier. High-frequency read endpoints such as GET /subscribers get a higher allowance than write and administrative endpoints. Limits are shared across all API keys for a project. Requests over the limit return HTTP 429 with rate-limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After).
Revenuecat Rate Limits is the machine-readable rate-limit profile for RevenueCat on the APIs.io network, in the API Commons Rate Limits shape.
It captures 7 rate-limit definitions, measuring requests.
Limit state is signalled in the X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Subscriptions, In-App Purchases, Billing, Mobile, and Entitlements.
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-ResetRetry-After
generated, dated 2026-07-01.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.