The newly introduced API endpoint for accessing group/community revenue data:
https://apis.roblox.com/transaction-records/v1/groups/GROUP_ID/revenue/summary/day
has unreasonably aggressive rate limits compared to the older, long-standing API:
https://economy.roblox.com/v1/groups/GROUP_ID/revenue/summary/day
This new endpoint is now being used in critical areas such as the Community Configuration page, and just navigating between the ‘Sales’ and ‘Summary’ tabs once or twice is enough to trigger a rate limit. Even worse, the UI does not display any indication that you’ve been rate limited — the page simply breaks with missing data, misleading users into thinking something else is wrong.
This is a major regression in usability.
Repro Steps:
- Visit a community’s configuration page.
- Switch between “Sales” and “Summary” tabs 1–2 times.
- Observe that the page breaks due to silent rate-limiting.
Expected Behavior:
- The page should not rate limit after just a couple of navigations.
- If a rate limit is hit, the UI should handle it gracefully and display an error rather than breaking completely.
- The rate limits should be equal to or more relaxed than the older API, especially for read-only access.
We run a program that logs pending Robux changes for certain groups in real time. It has successfully used the older API for months and checks the endpoint once every second without issues.
Recently, we attempted to migrate this to the new transaction-records API — and had to roll it back immediately. The rate limiting is not just strict — it’s unbearable. On DigitalOcean servers, a single request is enough to lock you out, and all subsequent requests return 429 errors for several seconds, if not longer. This simply cannot be intended behavior.
This is unacceptable for a service that was previously reliable and accessible. It severely disrupts analytics workflows, live dashboards, and financial automation tools. Roblox recently improved APIs like the Report Abuse endpoint by removing rate limits entirely, recognizing that this enhances user and developer experience. So it’s confusing and frustrating that a new read-only revenue endpoint — meant to replace the older one — would launch with even stricter limits than before.
If Roblox intends to deprecate the older endpoint (which seems inevitable), the following actions are urgently needed:
- Relax rate limits on the new API to match (or improve upon) the older one.
- Fix the revenue and sales UI to properly catch and handle 429 errors.
- Communicate transparently about these changes and their justifications.
How can the older API support requests every second without issue, yet the newer one breaks after a single request? Why does a modern upgrade introduce stricter limits and break core functionality? This makes zero sense.
A private message is associated with this bug report
@QuantumXayle Think this can be looked into? If you’re not on the team responsible, I’d appreciate if you could triage it to whoever is.