RevenueCat · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 7 rate-limit definitions, measuring requests.

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.

7 Limits Throttle: 429
SubscriptionsIn-App PurchasesBillingMobileEntitlementsRate LimitingQuotasThrottling

Limits

Get or Create Subscriber (GET /subscribers/{app_user_id}) endpoint
requests · minute
6000
High-throughput read endpoint for live subscriber lookups.
Create Purchase (POST /receipts) endpoint
requests · minute
1200
Receipt validation across App Store, Play, Amazon, Stripe, Roku, Paddle.
Update Subscriber Attributes (POST /subscribers/{app_user_id}/attributes) endpoint
requests · minute
6000
Attribute writes; batches multiple attributes per call.
Grant / Revoke Promotional Entitlement (v1) endpoint
requests · minute
300
Administrative entitlement operations.
Get Offerings (GET /subscribers/{app_user_id}/offerings) endpoint
requests · minute
6000
Paywall/offering resolution reads.
v2 Read Endpoints (GET /projects/**) endpoint
requests · minute
60
v2 management/read endpoints (projects, apps, customers, products, entitlements, offerings, packages).
v2 Write Endpoints (POST / DELETE /projects/**) endpoint
requests · minute
30
v2 catalog create/update/delete operations run at a lower administrative rate.

Policies

Per-Endpoint Limits
Limits are applied per endpoint, so heavy reads do not consume the write budget and vice versa.
429 Handling
On HTTP 429 clients should honor Retry-After and back off exponentially with jitter.
Header-Driven Backoff
Inspect X-RateLimit-Remaining and X-RateLimit-Reset to pace requests before hitting the limit.

Sources