Hello all,
We’re rolling out two new Beta rate limit headers on Jira and Confluence REST APIs for points-based quota limits. These headers follow a unified, structured model aligned with rate-limiting header standards. They are informational only; they don’t trigger enforcement or throttling. They are additive, and existing X-RateLimit-* headers are still returned. The rollout will be complete in the next 24-48 hours across all traffic.
Beta-RateLimit Headers Rolling Out on Jira and Confluence REST APIs
-
Beta-RateLimit-Policy- A static header that describes the rate-limit policy applied to the request.- Example: Beta-RateLimit-Policy: “global-app-quota”;q=65000;w=3600
-
Beta-RateLimit- A dynamic response header that provides usage signals for applicable rate-limit policies- Example: Beta-RateLimit: “global-app-quota”;r=13000;t=600
At enforcement, these headers will drop the Beta- prefix and become RateLimit-Policy and RateLimit. For points-based quota enforcement, only these new headers will be used.
For full details, including header format, parameters, and usage examples:
-
Jira Rate Limiting documentation: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/
-
Confluence Rate Limiting documentation: https://developer.atlassian.com/cloud/confluence/rate-limiting/