checkUserActivities or such, is no longer suppoted in the query params; the viewer's access token in the header would sufficeget endpoints accpets some query params to paginate your request.https://baseApi/users?pageSize=4pagination attribute (as typed above);// https://baseApi/users?pageSize=4
{
"success": true,
"statusCode": 200,
"data": [
"...",
{
"id": "some-last-user-id",
"email": "hiseous@gmail.com",
"displayName": "Hiseous",
"verified": true
}
],
"pagination": {
"lastEvaluatedKey": {
"id": "some-last-user-id",
"dateCreated": "2024-10-24 07:46:30.725Z"
}
}
}lastEvaluatedKey value;https://baseApi/users/?pageSize=4&lastEvaluatedKey={"id":"some-last-user-id","dateFollowed":"2024-10-24 07:46:30.725Z"}pagination attribute, you repeat the same process with the new pagination props from the newer response;// https://baseApi/users/?pageSize=4&lastEvaluatedKey={"id":"some-last-user-id","dateFollowed":"2024-10-24 07:46:30.725Z"}
{
"success": true,
"statusCode": 200,
"data": [
"...",
{
"id": "some-another-last-user-id",
"email": "hissy-baby@gmail.com",
"displayName": "Hiseous",
"verified": true
}
],
"pagination": {
"lastEvaluatedKey": {
"id": "some-another-last-user-id",
"dateCreated": "2025-10-24 07:46:30.725Z"
}
}
}lastEvaluatedKey, by the way.pagination, then it implies the last items were fetched.