Adapty Rate Limits
Adapty applies per-account rate limiting to its Server-Side REST API to protect platform stability. Adapty documents that server-side requests should be kept to reasonable volumes and recommends batching and caching where possible; exceeding limits returns HTTP 429. Specific numeric per-endpoint request-per- second/minute limits are not published in a reconciled table and vary by account and endpoint (profile reads vs. transaction writes). This artifact is not reconciled to exact values.
Adapty Rate Limits is the machine-readable rate-limit profile for Adapty on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests and events.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Mobile, Subscriptions, Server-Side, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://adapty.io/docs/getting-started-with-server-side-api
- https://adapty.io/docs/server-side-api-specs
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/adapty-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.