I would like to query all files exists in repository & apply pagination like below
https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/src/{node}?pagelen=10&page=2
But it always gives me 500 internal server error.
Here is some information from the documentation: https://developer.atlassian.com/bitbucket/api/2/reference/meta/pagination
However, clients are not expected to construct URLs themselves by manipulating the page number query parameter. Instead, the response contains a link to the next page. This link should be treated as an opaque location that is not to be constructed by clients or even assumed to be predictable. The only contract around the next link is that it will return the next chunk of results.
In your initial response (without the page parameter), you will find a URL to the next page of results.
Yes, I am able to see next page url in response but again new challenge is, I am not getting previous page url after I navigate to the next page. But document says paginated response will contain previous property if it can navigate to previous page? And somehow I am able to navigate to next page but unable to navigate to previous page, & I have to hack by keeping currentPage url in some variable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.