HTTP 429: Too Many Requests | AssetId Endpoint Error

We use the endpoint https://assetdelivery.roblox.com/v2/assetId/{assetId} to download place and model assets for our deployment process. For nearly 2 years, this has worked fine, however about 2 months ago, this endpoint started throwing a HTTP 429: Too Many Requests error after a single successful request and would continue throwing this error for 1 hour afterwards. This only happens when the requests are sent from our DigitalOcean services, I have tried on multiple home and office networks and it has consistently not given me a 429 error on those networks. I have tried moving our deployment service to a different IP and this still happens. Every request we have sent in order to test this has been using the same exact headers as our deployment service.

I would like to be able to use the Open Cloud API to do everything that we need to do which includes downloading place assets, downloading model assets, publishing places, and publishing model assets. Unfortunately, I have not yet begun migrating our deployment process to use the Open Cloud API because according to the documentation it is missing the ability to download place assets. This is a very essential step to automate in our deployment process because we have over 100 places that we need to download (or grab from a cache if the version hasn’t changed) from one experience, modify, and then upload to another experience.

Not a solution to the problem, but you could try temporarily using https://assetdelivery.roblox.com/v1/asset/?id={assetId} as a workaround, and seeing if it gets rate limited.

I’ve never seen this endpoint rate limited before.

It’ll give you a straight 302 redirect to the cdn, so you’ll need to update your logic to follow the redirect instead of parsing it from the v2 response.

2 Likes

Hi @Credenzio, are you still seeing issues with this?

I am. I tried it yesterday and after one request, I was rate limited.