We are excited to announce the launch of the Ordered Data Stores API beta on Open Cloud! This is an extension of our previous Standard Data Stores release.
Some of the use cases that can be enabled by this API include:
Read your in-experience leaderboard saved in Ordered Data Stores and show it on your website in real-time.
Map user keys that are stored in Standard Data Stores and migrate your schema.
To start using this feature, you can create an API key on the Credentials tab of Creator Dashboard and add permissions for your key to use Ordered Data Stores endpoints. The Open Cloud API maps the functionality of Lua ones, including entry read and write. You can set permissions for your API keys to read or write all the Ordered Data Stores for your experience.
We plan to release Ordered Data Stores for OAuth2 in the coming months. We will also work with you and incorporate your feedback for the general release, so please share any feedback you may have down below!
Ordered DataStores sounds like a good addition for our creators on ROBLOX, allowing external access to DataStores will definitely help if Developers wish to migrate user data to a different method of storing or access/edit it outside of the ROBLOX platform. Looking forward to seeing where this will go.
Thanks for this addition! It’ll serve as a very helpful asset to some of my external applications that require access to datastores to function.
A quick question; is there any official documentation for Open Cloud API request limits? I can’t seem to find any, especially for the MessagingService one. Knowledge of the rate limits for this service would be a huge help so I can ensure my systems are compliant with and do not exceed them.
I support this kind of thing but am concerned about outside uses that could be considered abuses and violations of the terms of service. Specifically about people being able to make USD purchases outside roblox and they’ll be able to set DataStore values, like buying Premium. Sure I support people not having a heavy for Robux, but is there any plan to avoid abuses like this?
Is there any plan on in the future of making OpenCloud API’s scale? Or Apply for higher limits at all?
Currently if you wanted to create a interactive website with your game, that i.e a user could log in and see their data, in truth this would work fine. But if you have a 80k concurrent players, you’d hit that limit pretty instantly.
Decent release I guess but we really need the option to view someone’s numerical placement in an OrderedDataStore. This is a very limiting factor and will be the reason the number of integrations will not be maximized.
One frustration is the lack of consistency in API naming. I know this is kinda minor, but it makes writing SDKs et. al. quite difficult. Some examples between this and the standard DataStore API:
Ordered uses ordered-data-stores in the path; standard uses datastores.
Inconsistency between “datastore” vs. “data-store”
Ordered uses orderedDataStores at end of path; standard uses standard-datastores.
Casing inconsistency; probably not great to have capitalization, e.g. “orderedDataStore”
Ordered requires scope in path; standard requires scope in query string.
Ordered pagination uses the naming of “token”; standard uses “cursor” (cursor is preferred IMO).
Query params in ordered use snake_case; standard use camelCase (and sometimes PascalCase…)
These are just the ones I’ve picked up on in the last hour of trying to add ordered datastore support to my rbxcloud tool.
I would like to strongly advocate for consistency across these APIs, especially as they expand. I don’t want to write tons of custom code for every single API just to handle naming convention changes.
!