I was using the POST endpoint for finding users by prefix and I noticed something weird when reading the responses from the API. Whenever a user prefix has more than one page of results the hasMore field is always true. I was searching for the name Sage and it has 5 pages worth of data, however when you try to receive the 6th page it returns an HTTP 500 status saying that there's no more resources to be found.
Page 5
Page 6
I'm also curious as to what people have done to circumvent this issue, any pointers would be helpful!
I was using the
POST
endpoint for finding users by prefix and I noticed something weird when reading the responses from the API. Whenever a user prefix has more than one page of results thehasMore
field is alwaystrue
. I was searching for the nameSage
and it has 5 pages worth of data, however when you try to receive the 6th page it returns an HTTP 500 status saying that there's no more resources to be found.Page 5
Page 6
I'm also curious as to what people have done to circumvent this issue, any pointers would be helpful!