Jira API rate limit: see what CogniRunner spends
Jira Cloud's API rate limit is three limits at once, an hourly points quota, a per-second burst limit and a per-issue write limit, and when any of them trips the REST API answers 429 Too Many Requests with headers that say which one. What Jira doesn't give you is a screen that says which app spent the quota. There's an open suggestion for exactly that, AX-1883 , with 49 votes and 43 watchers, and…
Atlassian's Jira Cloud API has four rate limits that work together: an hourly points quota, a per-second burst limit, and per-issue write limits. When any of these limits are reached, the API responds with a 429 "Too Many Requests" status code and provides headers that indicate which limit was exceeded.
Jira does not provide a built-in screen that shows which app consumed the quota. However, CogniRunner, a Jira workflow app, offers this functionality. After implementing the screen, the author tested it on a demo site and found that one listener run cost 2 requests and 3 points.
The rate limits reset at the top of each UTC hour. The hourly quota is shared across all tenants, with a default pool of 65,000 points. Apps can also be assigned to different rate limit pools (Tier 1, Tier 2, or Per-Tenant) depending on their usage patterns.
To view the rate limit headers for your own API calls, you can use the `curl` command with an API token. The headers will include the rate limit policy, current usage, and remaining requests. A 429 response indicates that a limit has been exceeded.
The rate limit headers provide information about the specific path being accessed and whether the limit is based on points or burst limits. However, the hourly quota is not displayed in the headers, as it is only relevant to apps and not to scripts.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
