No, we will not support all of them. Some are considered too high risk (for example, those that spend Robux, like CreateBadge), and others will not be supported because they do not align with company priorities or are already supported in existing Open Cloud APIs.
11 Likes
Currently, there are no plans to onboard the Developer Products API due to various implementation details. However, if this issue persists, I encourage you to submit a bug report. Reliability is a priority for us, and any API that consistently fails should be investigated.
7 Likes
Is there any reason why the read endpoints are seemingly not yet supported on the legacy parity API for badges?
Yes, most of them do not require authentication, so we decided we should focus on onboarding other endpoints instead.
the stricter rate-limits could cause problems for other legacy APIs
Yes, we are setting rate limits on a case by case basis and intend to set them sufficiently high for all APIs.
12 Likes
Just to follow up on this, @appletree008 is talking about adding OAuth and API key support for the existing dev products API.
Full Open Cloud support for dev products is on our radar and not ruled out; can’t make any promises either though. We’d like to do it, and feedback like this is a helpful prioritization signal.
@Bulldo344 FYI
5 Likes
I’m very happy to see progress regarding OAuth2 support and Open Cloud. I’m essentially just waiting to be able to write with group resources (bless that we have read now!) before I dip my toes in.
My number one use case has always been Roblox verification (allowing a Discord bot to cleanly and directly know a Roblox account for data tooling) and semi-automatic group management without the pain of cookies or “add this text to your description” type services.
3 Likes
Love it! Will we see Swagger documentation on other
apis.roblox.comendpoints? I really enjoy them.
This is TBD right now. Because we do have the existing docs (e.g. Swagger UI) we may not create the new apis.roblox.com docs for all API Sites. We will keep you updated.
Additionally, will it ever be possible for members of a group to authenticate OAuth apps with permissions in the group?
Are you asking about any scopes in particular? We may consider this in the future, but it is not on our roadmap this year.
Does the “Create group API keys” permission help solve your problem?
2 Likes
There are some particular ones that are useful (from dev perspective), such as asset, universe, universe-places, and universe-datastores. We make use of external tooling (Rojo, Lune, etc.) within our studio, and we’ve made things that help us with this workflow and move quickly.
Unfortunately, it is tedious to manually maintain API keys at scale (multiple groups, growing # of team members, granular permissions, etc.). I had hoped OAuth would get me like 90% there, but unfortunately not.
Thankfully yes, but in a weird way - I ended up creating my own API that you sign into with OAuth, it verifies your account, and creates API keys for you with the appropriate permissions based on who you are, what groups you’re in, and your roles in them.
Otherwise, no. That permission allows them to create an API key with any permission, which isn’t what I’m looking for here.
I’ve created a feature request thread so it can be better tracked internally (or something, at least): Allow group members to grant OAuth app permissions to groups they don't own
I look forward to really anything. I hammer a lot whenever these API things come up about documentation because there’s a lot going on under apis.roblox.com that simply has no docs at all.
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.
2 Likes
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.
1 Like
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.
3 Likes
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?
1 Like
Hi all,
We’re excited to announce that we’ve expanded our support for more API Sites!
- Groups API: the first set of endpoints, including GroupAuditLog, UpdateGroupDescription, UpdateGroupStatus, and more.
- Localization Tables API: Endpoints such as UpdateTableContents, GetTableEntriesPaged, and others.
- Game Internationalization API: Full support for GameIcon, GameThumbnail, and GameNameAndDescription endpoints.
For more details, please check out our documentation here .
4 Likes
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. 
1 Like
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.
- Develop API: The first set of endpoints, including UpdateTeamCreateSettings, GetMembersInTeamCreateSessionByPlace, CloseTeamTestGame, and more.
- Game Internationalization API: Support for SetSourceLanguage, SetSupportedLanguages, SetAutomaticTranslationStatus and a few more endpoints.
For more details, please check out our documentation!
3 Likes
Expanded API Support Now Available!
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.
Highlights
-
Badges API
- Update badge details
- More features coming
-
Develop API
- Fetch and update Team Create settings and members
- Additional features are in progress!
-
Followings API
- Follow, unfollow, and fetch followings
-
Game Internationalization API
- Update localized icons, names, and descriptions for badges, passes, developer products, and experiences
- Manage an experience’s source language and supported languages
-
Groups API
- Fetch and update group information, statuses, settings, and audit logs
- More updates are on the way!
-
Localization Tables API
- Fetch and update entries in localization tables
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.
We’d love to hear your feedback
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!
5 Likes
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.
1 Like
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.