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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/revenuecat-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.