We are working on a tool that synchronizes data between an application and Jira and we noticed that sometimes our requests sent to Jira return 429 error. We tried to identify which is the limit of the API requests, but we did not find any details on Jira Forums. Could you please help us to clarify how the concurrency API limit is calculated, so we can adjust our logic to diminish the number of responses with 429 error.
Thank you in advance!
It is dynamic and depends on many things, unfortunately (including other apps activity so you cannot predict it).
So, you should build a logic that postpones the requests if you get 429 response.
@KateBarariSevcenco, are you sure that it’s not related to ngrok connections limitation? It looks exactly like that.
For not authorized users: 20 connections limit.
For authorized but not paid accounts: 40 connections.
Check paid options here. Please note, that “connections” means not “request”. So if you’ll provide a Keep-alive connection it should resolve your issue at all.
Regarding the lack of documentation on rate limiting, I’ll try to research this and create an article.
Hi @dmorrow, is there any CDAC post announcing the availability of the documentation (https://developer.atlassian.com/cloud/jira/platform/rate-limiting/) or any other way to provide feedback on the new documentation?
This is a good point. I have created Rate limiting guide for Jira and Confluence for this.