ok, i might sound a bit uneducated on the topic for asking this but im a environmental designer after all, tho i will shoot my shot.
Ive been searching for documents about all the endpoints but i cant really seem to find a reliable list of all of them.
Even when i search up the swagger, not everything is always listed.
like this one
https://apis.roblox.com/developer-products/v1/universes/53603958/developerproducts?pageNumber=1&pageSize=50
I cant seem to find any swagger docs for it
I used to frequently rely on the “try it out” functionality, would really like to see this back soon.
We have never exposed docs for specifically apis.roblox.com, this change only covers migration of documentation for API sites ([product name].roblox.com/docs, where product name is not “apis”).
I recommend creating a new topic if legacy endpoint documentation for apis.roblox.com is important to you and what kind of use cases are not possible without having the endpoints that that domain serves (and assuming there are no Open Cloud replacements for those endpoints yet).
Hey there, where are you getting the idea that we are phasing out APIs?
Again, as this reply states, the only change here is where the swagger / open API docs live for legacy APIs. There are no other changes other than where the documentation lives for these APIs.
We are not decreasing (or increasing) the guarantees we provide for these legacy APIs. We have never given any stability or documentation guarantees for legacy APIs. There is no change in status quo.
We are not removing any documentation. The legacy API documentation content has been migrated 1:1 to the best of our knowledge to the new Creator Hub documentation resource. (just for emphasis, again, please do make sure to check the left navigation, not just the linked page)
If anything is missing that was there before (~2 weeks ago), please let us know what is missing.
Hi, thanks for creating a unified documentation for Roblox web APIs! For many years I’ve been maintaining a GitHub repository listing Roblox API sites and hopefully now I can simply point developers to this new page.
Are there any plans to fix the broken /docs links on legacy API sites? I understand that this new unified page is the future but I suspect there are hundreds of now-broken links. One option could be to redirect those /docs links over to the unified documentation page for as long as the API site is still available.
Hey, we’re in a complicated in-between state at the moment for various technical/safety reasons I can’t further elaborate on here, but yes the ideal state we want to work towards is that everything is on the new docs page and that we have automatic redirects. (apologies for late reply, missed your post until now)