Check your Roblox tools before API limits tighten
Selected cookie-authenticated and unauthenticated API routes will get lower limits after October 19. Check busy periods and shared request limits before changing your integration.
Roblox will lower rate limits for selected web API endpoints after October 19. The September 30 announcement covers routes in six services: badges, datastores, game persistence, inventory, thumbnails and users. It affects specified cookie-authenticated or unauthenticated IP requests; Open Cloud limits are unchanged.
For example, the thumbnails /v1/batch limit falls from 10,000 to 260 requests per authenticated cookie per minute. The users /v1/users/ limits fall from 1,000 to 100 requests per second for both listed authentication categories.
Read each row in the official tables carefully: they mix per-second and per-minute limits. Roblox says the new limits exceed observed peak usage, while unusual bursts could still trigger throttling. It lists Open Cloud alternatives for some routes and asks affected developers to report their use case and request volume.
Measure the busiest minute
Our recommendation is to list the exact routes used by your dashboard, extension or automation. Record the authentication method, request frequency and which jobs share an outbound IP or authenticated session.
Measure busy periods and restarts as well as average traffic. A background refresh, several simultaneous page loads and queued retries can arrive together even when the daily request count looks modest.
Use those measurements to limit the requests your jobs make together. Cache reusable results, combine duplicate work and spread scheduled refreshes over time. Test how the interface behaves when a request must wait: retain useful results and clearly label old data.
Where Roblox lists an Open Cloud alternative, compare its returned data and permissions before migrating. Replay your busiest measured workload against your own limiter, then monitor throttling and data freshness after deployment.