INTEGRITY Cloudflare Docs

Limits

Cloudflare GraphQL API exposes more than 70 datasets representing products with different configurations and data availability for different zones and accounts plans.

To support this variety of products, Cloudflare GraphQL API has three layers of limits:

Global limits

These limits are applied to every query for every plan:

Additionally, there is a limited number of queries you can make per request. The total number of queries in a request is equal to the number of zone/account scopes, multiplied by the number of nodes to which they are applied.

User limits

Cloudflare GraphQL API limits the number of GraphQL requests each user can send. The default quota is 300 GraphQL queries over 5-minute window. It allows a user to run at least 1 query every second or do a burst of 300 queries and then wait 5 minutes before issuing another query.

That rate limit is applied in addition to the general rate limits enforced by the Cloudflare API.

Account-based rate limiting

If you query analytics across many zones or accounts, you can opt into account-based rate limiting, where limits apply per account and per zone instead of per user or API token. Because each account and zone has its own budget, a single user or token can make far more requests overall, and limit increases can be applied per resource and take effect quickly.

To learn how to enable it and the query requirements, refer to Account-based rate limiting.

Node limits and availability

Each data node has its limits, such as:

Node limits are tied to requested zoneTag or accountTag. Higher plans have access to a greater selection of datasets or fields, and can query over broader historical intervals.

To get exact boundaries and availability for your zone(s) or account, please refer to settings.