API Token Rate Limiting

Announcements
1

Please note an important update regarding the use of API tokens. Starting November 22, 2025, Atlassian will implement rate limits for API tokens to ensure a consistent, reliable, and secure experience for all users.

How to find out if you are using API tokens

All admins who have unmanaged users for Jira and Confluence can learn about their API tokens from the Atlassian Administration screen. Learn how. If you are an unmanaged user, we will contact your admin directly if we expect you will be affected by API token rate limits.

These limits will affect any apps, scripts, or integrations relying on API tokens. If you are using API tokens, please review this documentation to learn more about the limits and best practices for lowering request costs:

In some circumstances, where integrations using API tokens heavily impact the stability of our platform, we reserve the right to enforce the limits at an earlier date. If you will be rate-limited before November 22, 2025, Atlassian will contact you directly.

We don’t expect the majority of customers to be affected by these rate limits. Our team is actively refining these limits and will publish them in the linked documentation in the coming months. Stay tuned for detailed information and any necessary adjustments.

Atlassian has also been rolling out additional rate limits for Marketplace Partner-developed apps, which we have shared with Marketplace Partners. As a customer, you don’t need to take any action; however, if you notice any Marketplace app not functioning as expected, please contact the respective Marketplace Partner for support.

Why this change?

Rate limits are a common industry practice and a proactive measure to safeguard our platform’s reliability, stability, and security by preventing integrations from overloading Atlassian’s systems. These limits support consistent quality of service and fair access to resources for all Atlassian customers.

Thank you for your understanding and cooperation as we work to enhance the security and reliability of our services.

Best regards,
The Atlassian Team

2

Just to clarify, previously announced Marketplace Partners: API rate limiting for free apps from August 2025 were just for Connect and Forge apps on Marketplace? And these “API Token Rate Limiting” from November 2025 are for external scripts/apps using API Tokens?

Will you send beta headers Beta-Retry-After, X-Beta-RateLimit-NearLimit, X-Beta-RateLimit-Reason, X-Beta-RateLimit-Reset for “API Token Rate Limiting” too?

3

@OndejMedek, yes, that’s right. This announcement is for all API calls that are utilizing API tokens.

We will be sending X-Beta- headers back the same way we’ve been doing it for the Marketplace apps.

4

Thanks for quick response. I have a few more quesions:

  1. Will these limits differ depending on Jira site pricing (free vs. standard vs. premium)?
  2. Is there any way how to test these headers, e.g. some mockup API or e.g. possibility to add some token or header to HTTP request to make the REST API endpoint behave like the rate limit has ben reached? (See also Rate limiting Testing which gives no help for us.)
  3. When HTTP response header X-RateLimit-Remaining is returned? I would expect it in every (successful, e.g. 200) response, but I do no see it there.
    Thanks
5

It always makes me smile when a company tries to enforce service degradation to end users by selling it as performance enhancements… :sweat_smile:

4 Likes