Skip to content

[Fundamentals] Update api-rate-limits.mdx #25023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[Fundamentals] Update api-rate-limits.mdx #25023

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/content/partials/fundamentals/api-rate-limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,13 @@ Some specific API calls have their own limits and are documented separately, suc
- [Gateway Lists API](/cloudflare-one/policies/gateway/lists/#api-rate-limit)

Enterprise customers can also [contact Cloudflare Support](/support/contacting-cloudflare-support/) to raise the Client API per user, GraphQL, or API token limits to a higher value.

The following headers that are always returned on calls to the Cloudflare API:

- `X-RateLimit-Limit`: Total Number of requests the caller can make
- `X-RateLimit-Remaining`: Number of requests before Rate Limit kicks in

And these headers are returned only when a rate limit has been reached (error code: 429):

- `Retry-After`: Number of Seconds until more capacity is available, rounded up
- `X-RateLimit-Reset`: RFC 1123 Formatted Date as to when more capacity is available
Loading