Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Using pagination for /2.0/repositories

We are maintaining a Bitbucket app. We have customer complaints that we are not showing all repositories. It seems this is a bug in the Bitbucket API.

The pagination seems broken. The request

returns the same result than

In fact, changing the number of page in the request parameter does not seem to have any effect.

There are the results from an impacted customer:

Page 1

$curl -H "Authorization: JWT <jwt>" '' | jq -r ".values[].slug"


Page 2

$ curl -H "Authorization: JWT <jwt>" '' | jq -r ".values[].slug"



The correct behavior should be to have a different list of values for each page.


Am I doing anything wrong?


Note: it would be really cool to be able to write content with markdown on this forum.

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 19, 2022

Hey Julien,

I have tested this from my end using AppPassword as the authentication method and was unable to reproduce this issue - I am able to see a list of 10 repositories belonging to my workspaceID and viewing page 2 shows the remaining 4 repositories attributed to my workspaceID:

curl -X GET \
--url '{workspaceID}?page=1&pagelen=10&role=owner' \
--user {username}:{AppPassword}

curl -X GET \
--url '{workspaceID}?page=2&pagelen=10&role=owner' \
--user {username}:{AppPassword}

NOTE: you will need to remove the curly braces and replace workspaceID, username and AppPassword with actual values.

Can you try the above and let me know how this goes?


- Ben (Bitbucket Cloud Support)

Hi @Ben and sorry for the late reply. We do not have the application user or their password. We have a Bitbucket App and only authenticate through a JWT. This is how Bitbucket Applications authenticate (link to Bitbucket doc).


To this day, we will have the issue and more customers complained.

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 19, 2023

Hi @Julien Delange 

My apologies - I have attempted to re-create your environment by creating a test app, and running a NodeJS server with Ngrok to be able to generate a JWT but I have been unsuccessful. I do not have much knowledge of NodeJS code so this is probably the main issue I'm facing :/

To avoid any further delay, I would suggest reaching out to our developer community as they would be better equipped to assist you further:


- Ben (Bitbucket Cloud Support)

Thank you! I created the following error (for traceability of folks that want to keep track of the issue)

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events