Buy Me a Coffee · Rate Limits

Buymeacoffee Rate Limits

Buy Me a Coffee does not publish an official numeric rate limit for its developer API in the public-facing documentation. The API is read-only and personal (scoped to a single creator's own account), so request volumes are naturally low. The Microsoft Power Platform connector that wraps the same API enforces a client-side throttle of 100 calls per connection per 60 seconds - a reasonable practical guideline, though it is the connector's limit rather than a value Buy Me a Coffee documents directly. Results are paginated (Laravel-style current_page / per_page / next_page_url), so large supporter, member, or Extras lists should be walked page by page rather than polled aggressively.

Buymeacoffee Rate Limits is the machine-readable rate-limit profile for Buy Me a Coffee on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and records.

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

Tagged areas include Creator Economy, Memberships, Payments, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Creator EconomyMembershipsPaymentsRate LimitingQuotas

Limits

Developer API Requests token
requests
not officially published
No fixed numeric request-rate limit is documented by Buy Me a Coffee for the developer API.
Connector Throttle (practical guideline) connection
requests
100 per 60 seconds
Enforced by the Microsoft Power Platform connector wrapping the same API; modeled here as a practical guideline, not an official Buy Me a Coffee value.
Pagination Page Size request
records
per_page (server-defined)
Collections return a fixed per_page count; walk next_page_url to page through supporters, members, and Extras.

Policies

Read-Only Access
The developer API is read-only (GET); tokens can be created with a read-only option in the Developer Dashboard.
Backoff Strategy
On a 429 response, implement exponential backoff with jitter before retrying.
Paginate Not Poll
Use next_page_url to page through large result sets instead of repeatedly polling the first page.

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