Wagtail Rate Limits
Wagtail's built-in REST API v2 does not impose rate limits at the framework level. Any rate limiting is the responsibility of the operator deploying the CMS and is typically enforced via a reverse proxy (nginx, Caddy), a CDN, or Django middleware. The following documents Wagtail's built-in pagination and result-limit controls, which are the closest framework-level constraints.
Wagtail Rate Limits is the machine-readable rate-limit profile for Wagtail on the APIs.io network, conforming to the API Commons Rate Limits specification.
Tagged areas include CMS, Content Management, Django, Python, and Headless CMS.
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/wagtail-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.