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

Limit not working while fetching data using REST API

Shruti Anantwar May 8, 2017

While fetching data usin REST calls from fisheye and crucile, the limit parameter is not working. Is there any alternative for it?

1 answer

1 vote
Piotr Swiecicki
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 8, 2017

Hi Shruti,

Please note not every FishEye/Crucible REST API method supports pagination, the ones that do support have it explicitely mentioned in the documentation. 

Let me know what URL are you trying to hit so I can clarify if pagination is supported for this endpoint or if there is alternative paginated endpoint that could be used instead. 

Shruti Anantwar May 8, 2017

Hi, I tried limiting data while fetching repositories. Here's the query,

http://localhost:8060/rest-service-fe/repositories-v1?limit=1

Inspite of applying limit=1, I'm getting all the list of repositories. I am facing same issue with other queries as well (Eg. users, revisionInfo etc).

Piotr Swiecicki
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 8, 2017

note GET request to https://docs.atlassian.com/fisheye-crucible/latest/wadl/fisheye.html#rest-service-fe:repositories-v1 resource lists all the repositories, while GET request to similar https://docs.atlassian.com/fisheye-crucible/latest/wadl/fecru.html#rest-service-fecru:admin:repositories resource retrieves a page of repositories.  The latter use paginated API.

Similary use https://docs.atlassian.com/fisheye-crucible/latest/wadl/fecru.html#rest-service-fecru:admin:users to retrieve page of users etc.

Hope that helps

Shruti Anantwar May 9, 2017

Hi Piotr,

It worked. Thanks a lot! :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events