What is the rate limit value for the api calls made to Jira?

[sanjeev.pande]

We have been facing issue with the api rate limits recently.

We would like to know what is the rate limit count today for the api calls that are made to Jira, assuming the rate limit is managed at the level of tenant/user/app-user.

Also, is there any recent change that Jira has made regarding the api rate limits ?
We do see that the document has updated recently.
https://developer.atlassian.com/cloud/jira/platform/rate-limiting/?_ga=2.105859072.2068921315.1605000191-1043247589.1599447605

Thank you,

[ibuchanan]

We have been facing issue with the api rate limits recently.

Can you explain what the issue is? Does your code already back-off after receiving HTTP status 429?

… assuming the rate limit is managed at the level of tenant/user/app-user.

As explained in the documentation to which you linked:

Rate limiting is implemented as a set of rules that take into account the number of threads handling certain kinds of requests, the cost of the requests, and the resources required by the requests.

Each rule applies to a unique combination of resources such as nodes, tenants, database hosts, endpoints, or compute resources. Rules are evaluated in a sequence designed to maximize computational efficiency.

Each rule has its own rate threshold and its own counter to track request processing. Request processing above the threshold is blocked, including downstream processing. Cost calculations that involve other rules can also figure into rate limiting, since different requests can require different types and amounts of resources.

REST API rate limits are not published because the computation logic is evolving continuously to maximize reliability and performance for customers.

In short, we can’t give you a simple number of as a request rate because the limits aren’t based on your assumption of tenant, user, and/or app-user.

Also, is there any recent change that Jira has made regarding the api rate limits ?

The new documentation is our attempt to document a previously opaque topic, not a change in the technology. That said, our site reliability engineers do sometimes apply additional limits if they detect something they consider to be API abuse. This can mean an app that was making, for example, 20 API requests per second, is suddenly capped to, for example, 2 API requests per second. These additional limits are applied per tenant. The best way to resolve such a case is to first implement the rate limiting precautions listed in the rate limit documentation, then work with your customer through Atlassian support to remove the abuse flag.