If I were going to make 20000 API calls in a row to a cloud instance, would there be any impact?

[Steven Becherer]

We're planning on updating issues through the API, and what we have will require an API call to be made for every issue:

GET https://developer.atlassian.com/cloud/jira/platform/rest/api/2/issue/SKP-1/editmeta
UPDATE https://developer.atlassian.com/cloud/jira/platform/rest/api/2/issue/SKP-1

If we have 23,000 issues and 2 calls for each - would we need to do this in batching or is it possible to do this in one go?

In general just to ask directly - what is the API call limit be rate throttling applies? Are there any costs financially as well for making this many API calls in go?

Thanks in advance

-Steve

[Aaron Pavez _ServiceRocket_ · Accepted solution]

Hi @Steven Becherer 

You can check the Rate limit here:

https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

Add to your code to capture the 429 error and set a pause/retry after some calls.

Regards

[Steven Becherer]

Hey thanks for the quick reply! So I see this part here: REST API rate limits are not published because the computation logic is evolving continuously to maximize reliability and performance for customers.

I think my question would be related to this. What you said makes sense with the 429 check, I think doing this in batches is probably what is safest and then using the 429 as an additional check. Thanks Aaron!