Hi @sunnyape following up here. To note, the new quota and burst based limits do scale based on plan type and on seats. For example, a standard plan with 1,000 seats would get higher limits than 500 and one with 1,000 seats on premium would also receive more limits than 1,000 seats on standard.
1 Like
Hi @janette Thank you for your insightful feedback. We have shared your comments with the product and engineering teams responsible for rate limiting in both Jira and Confluence. Rest assured, we will investigate these instances further. We fully recognize the frustration that arises from bugs and other situations that lead users to make additional API calls. While we do not anticipate that these extra calls will exceed your rate limits, we recommend closely monitoring the headers, particularly during these occurrences.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Hi @Floating-electron this is not related. However, to ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Hello and thank you for your questions and feedback. It would only be the 429 responses. I have shared your comments with the product and engineering teams responsible for rate limiting in both Jira and Confluence.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
We recommend closely monitoring the headers, particularly during these occurrences. If you feel you need more than the headers to monitor your usage, please do let us know. Thank you
Hi @jbevan this is not actual rate limiting and instead a warning that they could be surpassed once enforcement is live.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
hi @tobias has this been resolved? To note, in order to ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Hi @ernst.stefan thank you for the feedback. At this time, we recommend monitoring the header responses.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
Please do let me know what else you have in mind if the headers are not sufficient enough.
Hi @tbinna Thank you for your insightful feedback. We have shared your comments with the product and engineering teams responsible for rate limiting in both Jira and Confluence. Rest assured, we will investigate these instances further. We fully recognize the frustration that arises from bugs and other situations that lead users to make additional API calls. While we do not anticipate that these extra calls will exceed your rate limits, we recommend closely monitoring the headers, particularly during these occurrences.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Hi @remie Thank you for your feedback. At this time, we unfortunately do not have any more details to share but I have passed the request for more specific information on to the team around which endpoints are seeing spikes.
In the meantime, we recommend closely monitoring the headers, particularly during circumstances by which you have to make additional calls or face any bugs.
And in order to ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
Hi @klaussner Thank you for your insightful feedback. At this time, we unfortunately do not have any more details to share but I have passed the request for more specific information on to the team around which endpoints are seeing spikes.
We fully recognize the frustration that arises from bugs and other situations that lead users to make additional API calls. While we do not anticipate that these extra calls will exceed your rate limits, we recommend closely monitoring the headers, particularly during these occurrences.
To ensure Marketplace partners are able to decipher whether or not they’re facing actual rate limits, we have rolled out beta- prefixed headers. These will appear to notify partners that they would have breached the upcoming quota and burst based rate limits. The headers will be as follows:
- Beta-Retry-After
- X-Beta-RateLimit-NearLimit
- X-Beta-RateLimit-Reason
- X-Beta-RateLimit-Reset
However, if you do receive headers without beta-, be advised that you are facing rate limits.
hi @adam Thank you for your the feedback. At this time, we unfortunately do not have any more details to share but I have passed the request for more specific information on to the team around which endpoints are seeing spikes. We fully recognize the frustration that arises from bugs and other situations that lead users to make additional API calls. While we do not anticipate that these extra calls will exceed your rate limits, we recommend closely monitoring the headers, particularly during these occurrences.
Hi @KelseyVanScoy,
According to the Atlassian documentation on Jira Cloud rate limiting, a new rate limiting system is scheduled to go into effect on November 22, 2025. I’ve added logging for these upcoming limits, but across all my applications—regardless of context—I consistently observe the same response for each API call:
retryAfter: 1
rateLimitReason: jira-burst-based
This behavior seems unexpected. Could you clarify the current status of the new rate limiting system?
1 Like