Handle API rate limit in forge app for JIRA

Hello Community,
I am working on developing one forge app which get data from third party API and create issues in JIRA based on those data.
While making API call to JIRA to create issues I am getting 429(Too Many Requests) error. Is there any specific API rate limit (like only ‘X’ numbers of API calls in ‘Y’ sec. ) that I need to follow to get rid of this errors?
Also I wanted to know that if I use bulk create issue API then can I be sure that what data I pass in the request body, issues will be created in the same sequence means response will have one list of issue keys which were created, are these issue keys in the same order as the data we pass?

Hi @DarshanVarasani
About rate limits - here is a page with different kind of limitations for forge: https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/#async-events-limits I believe you’ll find here the limits you’re interested in.
About the bulk create - the order of sequencing issues to be created and the created issues in the response should be the same however, it’s not guaranteed so it may change in the future.


1 Like

Hi @PawelRacki thanks for the clarification regarding bulk create.
About rate limit - the link you shared is about forge platform limit and I am interested in API rate limit for JIRA cloud APIs (like only ‘X’ numbers of API calls allowed in ‘Y’ sec. ) for any platform.

Oh, sorry about that. However, I can’t tell you what are the exact rate limits cause they are not published. Here is a page about that: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/ and a quote from the page: “REST API rate limits are not published because the computation logic is evolving continuously to maximize reliability and performance for customers.” However on the same page there is an example with pseudo code that illustrates the recommended response processing logic: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/#response-handling-pseudo-code

1 Like