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/editmetaUPDATE 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
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
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!
It looks like you're new here. Sign in or register to get started.
![Photo of Aaron Pavez [ServiceRocket]](https://us.v-cdn.net/6038660/uploads/avatars/7e/e6/n7ee649f7a133f6ddee9b664969d38104.png)