Unable to fetch more than 700 servers servers using the Games V1 API (games.roblox.com/v1/)

When fetching public server instances for a given PlaceId using the Games v1 API, pagination stops prematurely. The nextPageCursor is returned as null after fetching 700 server(s) worth of pages, even though additional servers still exist.

:warning: Please read the update below this post before continuing reading, as it provides further information :warning:

Endpoint

GET https://games.roblox.com/v1/games/{placeId}/servers/public

Query Parameters

sortOrder=2
excludeFullGames=true
limit=100
cursor={cursor}

Behaviour

  • Pages 1–6 return valid nextPageCursor values.

  • Page 7 returns nextPageCursor: null.

  • Unable to progress with pagination even though more public servers exist for the place.

Steps to reproduce

  • Choose any active PlaceId with a large number of public servers.

  • Call the endpoint with limit=100.

  • Continue paginating using the returned nextPageCursor.

  • Observe that after ~7 pages, the response returns nextPageCursor: null.

This occurs consistently across:

  • Multiple PlaceIds

  • Multiple accounts

  • Different IP addresses

  • Manual requests and automated scripts

Additional Notes

  • The requests are authenticated with .ROBLOSECURITY as there is (or was) a hidden ratelimit for unauthenticated requests.

  • Reproduced by multiple users.

  • A third party was provided a cursor from page 6 and themselves received a null nextPageCursor on the following request, ruling out IP ratelimits.

  • While the official documentation states that serverType should be either 0, 1 passing public is also valid.

Expected behavior

  • The API should continue returning a valid nextPageCursor as long as additional server pages exist.

  • Pagination should only end when all servers have been exhausted.

Update

After further investigation, I’ve deduced that it isn’t a page limit, it’s a server limit. Roblox refuses to return more than 700 servers worth of pagination. The title & post has been updated slightly to reflect this, but please keep it in mind as you’re reading.

Update 2

Nevermind, I tried fetching again with a 50 server limit, and still encountered the nextPageCursor: null 7 pages deep.

This is intentional behaviour [Test] Updates to Server List Page