What does "X-Request-Count" means in BitBucket API response header?

#1

I saw there is a header name X-Request-Count in BitBucket API response header. What does it mean?

Does it mean I’ve made X requests in total? Based on what period? Per day? Per month? Lifetime?

Does it mean I have X left in the rate limit balance pool?

I’m trying to find a way to see how much left in my BitBucket rate limit balance pool. Something like this. Is there any?

1 Like
#2

I’ll address the 2 questions separately.

there is a header name X-Request-Count in BitBucket API response header. What does it mean?

This is an internal metric that isn’t useful to vendors or end users.

I’m trying to find a way to see how much left in my BitBucket rate limit balance pool.

Currently there is not a way to check your rate limit budget based on response headers. We plan on changing how rate limiting works for Connect apps soon, and so might revisit this and see if we can expose the budget in responses. One useful thing to keep in mind is that Bitbucket Cloud’s rate limiting is per-account being targeted, so if you are making API requests to 4 different accounts, there are actually 4 different budgets in play.

2 Likes
#3

@idick (or anyone else from Atlassian), any updates on this? We’re hitting our API limit constantly from Jenkins and it causes a ton of problems. Some better way to retry other than exponential backoff would be nice.

I know it’s a different product, but JIRA seems to have some pretty good answers to this problem.