As the result size is limited to 200 records, we are using parallel requests using the start parameter in order to retrieve rapidly the full result list. With the new cursor parameter, we need to do the same job sequentially which will take too much time to render, is it possible to increase at least page size to 1000 records ?
Regards
Does the new /rest/api/search/user REST API actually work with AP.Request?
I can get results from the browser, but nothing if I use AP.Request (no error, just zero results).
I just noticed it works in one context and not in another - the only difference is that one app is using JWT authentication and the other none. Does this mean apps must use JWT for /rest/api/search/user to work? The documentation only mentions requiring an app scope of read.
@james.dellow Have you tried again? There were some issues with AP.request and under what permission scope it was running, but that should be fixed by now.
This has been solved in the other thread and is not related to the search APIās listed in this deprecation notice.
No, it still doesnāt work with authentication set as none.
Would be nice to see that documented if thatās intentional.
Hi Jason,
Any updates on this?
The Atlassian team is currently working through a better process for this, which we hope to communicate in the coming weeks.
Cheers,
Brendan