Hopefully we can get a consolidated docs page (similar to the old
api.roblox.com/docs) again sometime soon, especially as more formerly documented APIs get deprecated/removed and migrated there. I’ll create a feature request for this too if there isn’t one already, maybe that helps move this further.
We created a new docs section for legacy APIs here, and because of this, we will not be supporting the swagger docs on the apis.roblox.com domain going forward for these legacy APIs.
Hi everyone,
We’re excited to announce that we’ve expanded our support for new API Sites! Game Internationalization API’s Badge, Developer Product, and Game Pass endpoints now support authentication through both API Key and OAuth.
For more details, please check out our documentation here.
It isn’t very clear via the OpenCloud API page that this only supports internationalisation of these types; I was trying out the developer products legacy API thinking it would allow me to update the price of a developer product only to figure out that isn’t the case. 
I see. Did you see the Swagger doc links at the top of the page? They provide comprehensive details, but I agree that we can make them more visible. Additionally, we could add a brief description for each endpoint or perhaps include a summary of the API site to provide quicker context. Would that help?
Hi all,
We’re excited to announce that we’ve expanded our support for more API Sites!
For more details, please check out our documentation here .
I was under the impression that this was a new release and perhaps just wasn’t documented yet.
Shouldn’t UpdateGroupNotificationPreference require a user level permission rather than just a manage group permission? I would be under the assumption that updating notification preferences is something on the individual user level rather than the group itself, or is this just a misleadingly named API due to some legacy behaviour? Unfortunately, this released on the one week in which Swagger docs are down so I can’t go and try it out for myself to confirm. 
Thanks for reporting this. You’re correct, the scope should be updated. We are working on a fix for this and will have the api updated by Monday.
Hi everyone,
During the past week we have onboarded several more endpoints.
For more details, please check out our documentation!
We’re thrilled to announce that we’ve rolled out support for 68 endpoints across 6 different APIs, each compatible with API Keys and OAuth 2.0 access tokens. You can explore the complete list of endpoints in our documentation.
Badges API
Develop API
Followings API
Game Internationalization API
Groups API
Localization Tables API
With these new endpoints, you can manage and update content for experience testing, releasing updates, and group management. And that’s not all - we’re working hard to release more endpoints soon, so stay tuned.
Your input is invaluable to us as we continue to work on more APIs. If you have suggestions or run into any issues, please don’t hesitate to share your thoughts with us!
YES, YES, YES! 
When will developer product API be supported? Experiencing a lot of "internal server errors’ and other internal errors that are the same - we depend on this for our service Parcel. Thanks for your help!
As @Bulldo344 implied, this is amazing 
Can we expect to see the API responsible for changing a users’ group role supported soon? Also, does the coverage right now include the ability to delete group wall posts, for example? Sorry for my confusion, it’s just that it’s not too clear which exact endpoints are supported, if not all of them.
Which specific endpoint are you seeing the internal errors on? I checked the metrics, and I didn’t observe any endpoints with elevated internal server errors.
As for supporting the Developer Product API, we’re actively discussing it. There are some technical challenges we’re working through before we can provide full support.
https://apis.roblox.com/developer-products/v1/universes/6620683937/developerproducts?pageNumber=1&pageSize=50
It is currently when it is called daily for updating information relating to developer products with proper ratelimits in place.
Some of the error codes we’ve received are:
500 status code.
and then some games return data, but it wouldn’t return them for another game. It really depends on the day.
Any idea when we will see ranking, and exiling release on legacy-groups?
Hi everyone,
During the past week we have onboarded 3 more endpoints.
For more details, please check out our documentation !
Considering this API already has a replacement with the non-legacy scope, shouldn’t the docs pressure the developer not to use this API route and to use the Open Cloud version of it?
Excited to see that legacy scope is getting a lot of updates. Hopeful to see updating user role / kicking group members soon!
Hey @sloss2003, the GetPendingGroupJoins API is different than the existing API linked. The legacy API allows you to get pending group join requests for a given User. Let us know if you have any other questions or concerns.
We have more API’s on the way and are glad you’re excited with the recent updates!
Hey @sloss2003 , group ranking and bans is on our teams radar and will arrive on legacy-groups or official Open Cloud soon.
Hi everyone,
During the past week we have onboarded 3 more endpoints.
For more details, please check out our documentation !
This is amazing, thank you for all of your work! Do we have an estimated ETA on when developer product API will hit Open Cloud or a much nicer developer API on the legecy docs? Current one does not handle all of the status codes we’ve recieved (most of the 200 for auth and some of the misc ones)