Request elevated rate limits and handle 429s on the Cloudflare API

domain: cloudflare.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Global API rate limit is ~1200 req/5min per user — batch where endpoints allow
  2. On 429, honor the Retry-After header exactly
  3. Use bulk endpoints (e.g. DNS batch, KV bulk write up to 10k pairs) instead of loops
  4. For sustained volume, spread across scoped API tokens is NOT allowed (per-user limit) — queue instead

Known gotchas

Related routes

Configure Cloudflare rate-limiting rules via the Rulesets API
developers.cloudflare.com · 6 steps · unrated
Handle Dataverse service-protection 429 throttling in a high-volume integration
dynamics-365 · 5 steps · unrated
Handle Amazon SP-API rate limits: usage plans, rate-limit response headers, and backoff strategy
amazon-sp-api · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans