Appwrite · Rate Limits

Appwrite Rate Limits

Appwrite's published rate-limit behaviour. This file replaces a 2026-05-04 scaffold whose per-tier requests-per-minute numbers were invented — Appwrite does not rate limit by plan tier at all, and recording it that way described a different product.

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

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

Tagged areas include Applications, Backends, Mobile, Open Source, and Rate Limiting.

0 Limits Throttle: 429 Quota: 429
ApplicationsBackendsMobileOpen SourceRate Limiting

Policies

Client-only enforcement
Rate limits apply to Client SDKs. Server SDK calls authenticated with an API key are exempt.
Reset computation
Clients must derive the wait from X-RateLimit-Reset (UTC epoch seconds); no Retry-After is sent.
Free-plan bandwidth exhaustion
On the Free plan, exhausting bandwidth denies API access entirely until the plan is upgraded — a quota consequence more severe than throttling.

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/appwrite-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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