To streamline our API offerings and provide a smoother developer experience, we will be deprecating several asset-related endpoints in the Develop API on July 1, 2025. These endpoints are being replaced by their equivalents in the Assets API, which offer enhanced functionality and a more consistent design. As part of this transition, we’re created replacements for Archive/Restore endpoints in the Assets API to ensure full feature parity with our deprecated Develop API endpoints.
Deprecating assets endpoints on Develop API
The Develop API has served our long-time developers well, but it’s time for an upgrade! With the exciting new features and increased functionality in the Assets API, we’re ready to deprecate several endpoints from the Develop API. This includes all endpoints under https://develop.roblox.com/v1/assets and https://develop.roblox.com/v2/assets. To ensure a smooth transition, we encourage you to migrate to the new Assets API endpoints as soon as possible.
We’re committed to providing a best-in-class experience for asset creation and management. We hope this update is a testament to that commitment. In the coming year we have exciting new additions planned, but we would love to hear your feedback, so please share below. Thank you!
So this will break older games further? Many unmaintained classic games will lose practically everything besides the parts and models? Filtering Enabled, part 2!
@CosmoCone@JellyM015 These are web endpoints, not engine API members. If you are not hitting exactly these endpoints directly in your external tooling or in your in-game code via a http proxy via HttpService, there is no impact to you.
But not for https://apis.roblox.com/assets/user-auth/v1/assets/{assetId}. I wonder if the user-auth one just uses the Cookies compared to the other one.
Ohhh, wait the alternatives listed are Open Cloud APIs. Okay, so that means it needs the API Key. That’s why it is saying that error, I think.
I think it would be great if the post mentions that the alternatives are part of the Open Cloud APIs. I believe otherwise, it is too difficult to distinguish which apis.roblox.com endpoints are part of the Open Cloud.
In my opinion, the previous version of the archive/restore API was better. Also, now it can hurt older games even more that use the previous version of this API.
You can’t even make requests to these domains/APIs without using an external server… Which means if the game is unmaintained the owner of said game is likely not going to maintain the webserver and the game will break on its own immediately.
