rest/agile API can anyone get pagination to work - &startAT &maxResults

[Paul Prachyl]

I'm trying to use the rest/agile/1.0 api with the paginations parameter &startAt=0&maxResults=100 and I get a 404 response. If I leave off the &startAt=0&maxResults=100, the api call works and I get the first 50 results, but I can't seem to use pagination. I'm wondering if it is a bug. I see the same results on any rest/agile calls

Example call

https://validate.site/rest/agile/1.0/board/314/sprint - returns information on sprints within board 314

but 

https://validate.site/rest/agile/1.0/board/314/sprint&startAt=0&maxResults=100 - returns a 404

[Paul Prachyl · Accepted solution]

well that didn't take long, looks like I need to use a ? instead of a & before startAt

https://validsite.net/rest/agile/latest/board?startAt=101&maxResults=100 - this works

https://validsite.net/rest/agile/latest/board&startAt=101&maxResults=100 - this fails

an & works with the other parts of the rest API

[David Bakkers]

Hello @Paul Prachyl

In Jira's REST API queries, like most others, a question mark is the delimiter that's used to start the sequence of parameters, and the ampersand is the delimiter for any subsequent parameters.

IE, all of the following queries to the board endpoint would be valid:

/rest/agile/latest/board?type=Scrum&startAt=101&maxResults=100

/rest/agile/latest/board?startAt=101&maxResults=100&type=Scrum

/rest/agile/latest/board?startAt=101&type=Scrum&maxResults=100

/rest/agile/latest/board?maxResults=100&type=Scrum&startAt=101

As long as the parameters are provided, their order is irrelevant.