REST API Rate Limiting ?

[ramchandrakar]

As mentioned on link https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html?_ga=2.203178583.73210821.1535348546-917214299.1534745397 17  there is Rate Limits for Bitbucket.

I am using this below mentioned api  to create issues in Jira.

https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-screenscheme-get 

https://your-domain.atlassian.net/rest/api/2/issue

As per our current project architecture we are creating one issues per api call.

So we are trying to make 1000 issues, but its failing only 100 issues are getting created in Jira. Is there any limits for create  issue and get issues API call.

Like how many request can we  make per minute or per hour ?

[Andy Rusnak]

Hi Ramchandrakar,

Welcome to the Atlassian Community!

There are rate limits on the REST APIs for Jira as well. This limits are put in place to ensure that services are reliable and responsive. The rate limits are not published as they are a based on on computational logic to maximize reliability and performance.

Having said that, there are ways that an API can detect if a rate as been hit and potentially handling that could be built into the API. The 429 response code indicates that a rate limit has been hit and these response may include a Retry-After or X-RateLimit-Reset header in the response. These headers can indicate how long the app needs to wait before issuing the next request. Additional information can be found at the Atlassian Developer Rate Limiting documentation.

So if your API requests are getting returned with a 429 response code after 100 issues are created for example, you may be able to handle that within the app calling the API.

Does help to answer your question on why you are likely seeing the behavior you are observing? If not or if I have misunderstood your scenario plese let me know and I would be happy to discuss further.

Thanks,

Andy