Getting "Rate limit for this resource has been exceeded" for team repositories

Issue #11169 resolved
Oskar Risberg created an issue

Good morning!

I just noticed we're having some trouble with loading all the repositories for our team.

The requested url is https://bitbucket.org/api/2.0/repositories/{teamname} and we loop over all the paged results.

I can't seem to find any information about any rate limiting on that URI, is there something i'm missing?

The team name is "fbinhouse"

I've found another endpoint for the exact same thing (https://api.bitbucket.org/2.0/teams/{teamname}/repositories), is it better to use one or the other?

I've also noticed there seems to be an undocumented "pagelen" var with a limit of 100 you can set, is that something we could use to reduce load or is that something that will disappear?

Thanks for a great service.

Comments (4)

  1. Erik van Zijst

    I can't seem to find any information about any rate limiting on that URI, is there something i'm missing?

    There currently is none on that endpoint.

    I've found another endpoint for the exact same thing (https://api.bitbucket.org/2.0/teams/{teamname}/repositories), is it better to use one or the other?

    One is a convenience 301 redirect for the other.

    I've also noticed there seems to be an undocumented "pagelen" var with a limit of 100 you can set, is that something we could use to reduce load or is that something that will disappear?

    Every paginated response in the 2.0 namespace supports this as per: https://confluence.atlassian.com/display/BITBUCKET/Version+2#Version2-Pagingthroughobjectcollections

  2. Oskar Risberg reporter

    Thank you so much!

    Didn't think about going over the general documentation just checked the endpoints i was at for the pagelen. Sorry about that.

    Great that the documentation is updated and thanks for a great service.

  3. Log in to comment