Memberful · Rate Limits

Memberful Rate Limits

Memberful does not publish specific numeric rate limits for its GraphQL API in its public developer documentation. As with most GraphQL endpoints, effective throughput is shaped by query complexity and cursor-based pagination (callers page through members, subscriptions, and orders with first/after rather than pulling everything at once) rather than by a documented per-minute request cap. OAuth access tokens are short-lived (15 minutes) with one-year refresh tokens, which naturally bounds token churn. The numeric limits below are MODELED as sensible expectations and are not confirmed by Memberful.

Memberful Rate Limits is the machine-readable rate-limit profile for Memberful on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, complexity, records, and minutes.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Memberships, Subscriptions, GraphQL, Rate Limiting, and Quotas.

4 Limits Throttle: 429
MembershipsSubscriptionsGraphQLRate LimitingQuotas

Limits

GraphQL Requests account
requests
not published
No fixed numeric request-rate limit is documented for the GraphQL endpoint.
Query Complexity request
complexity
not published (modeled)
GraphQL throughput is governed by query depth/complexity and pagination rather than a simple request count.
Pagination Page Size request
records
cursor-based (first/after/last/before)
Large result sets are traversed with cursor pagination; a maximum page size may apply but is not documented.
OAuth Access Token Lifetime token
minutes
15
Access tokens expire after 15 minutes; refresh tokens are valid for one year.

Policies

Cursor Pagination
Page through members, subscriptions, and orders using first/after (or last/before) instead of unbounded queries.
Backoff Strategy
On a 429 response, retry with exponential backoff and jitter and honor any Retry-After header.
Query Efficiency
Request only needed fields and keep query nesting shallow to reduce server-side complexity cost.

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/memberful-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.