How to add pagination to Search Issues ( picker ) API?

[Raghav Mishra]

We're using an API to search Issues on Jira, (Get issue picker suggestion).
The response is somewhat like this: 

Response: 

"sections":[
 {
   "label":"History Search",
   "sub":"Showing 2 of 2 matching issues",
   "id":"hs",
   "issues":[
   {issue_1 and details},
   {issue_2 and details}
  ]
 }
 ]

I want to implement Pagination for the issues i'm receiving. I tried adding startAt and maxResults value in query params, but the result does not change and gives me a non paged response. 

Is there anyway I can limit my values with pagination 
References: 

1. API Used 
2. Community solution for pagination

[Sunny Ape · Accepted solution]

Hello Raghav. Not all the REST API endpoints return the results in a paginated format, only those whose operation could potentially produce a very large number of results.

The /rest/api/3/issue/picker is one of the endpoints that does not return the results in paginated format, so defining the startAt and maxResults parameters has no effect. You will have to manage the results returned in your code.

[Raghav Mishra]

Thanks @Sunny Ape 
will I be able to add pagination if I search Issues by JQL search? 

JQL Search API

[Sunny Ape]

Yes.

In the REST API documentation for that endpoint, you will see that it specifically describes using startAt and maxResults to paginate the results:

startAt

integer

The index of the first item to return in a page of results (page offset).

Default: 0, Format: int32

maxResults

integer

The maximum number of items to return per page. To manage page size, Jira may return fewer items per page where a large number of fields are requested. The greatest number of items returned per page is achieved when requesting id or key only.

Default: 50, Format: int32

[Raghav Mishra]

Thanks @Sunny Ape We've moved our APIs to JQL and are able to paginate data now.