I believe that is the error that comes up from not having enough permissions. Make sure that for the API key you are using, the permissions section looks like this:
That is:
Hey @Skrateboard, hate to necrobump this topic. But I’m curious if you’ve had a chance in the last 10 months to take a look into Asset Management 
Currently overhauling game data and assets!
Hey, just saw this message now.
So far I don’t have a good plan for assets but it is something I’m considering adding now if it would be useful somehow. The thing I need to understand to make it work well to is know why you’re looking to handle assets in a tool like this rather than just doing it in Studio. What are the shortcomings of the Studio interface that make you want something else? Is it just for being able to let people upload based on API keys you can hand out or more than that?
In other news, I have been very slowly working on a new release that I hope to have ready soon. If I get it done by tomorrow I’ll hit my goal of technically less than a year between updates. This one is focused on cleaning up the interface in a few places as well as rounding out support for interacting with ordered datastores (and also fixing reading from them because Roblox changed the API 
). Expect more details soon.
Thanks so much for your response.
We were overhauling our game experience from one group to another - which presented the issue of asset transfer for asset textures that were originally uploaded to the first group (from multiple people/sources). For a couple hundred textures, we were hoping to export them out of Roblox (via your plugin) and reimport them via tarmac (as that was our new preferred format of asset management).
I realized pretty quickly after making that post that we could do this on our own! So not a problem at all! But thanks for your response - and this tool - really appreciate you!
Finally, after just over a year a new release is ready. This one is focused on completing support for Ordered Datastores but it also has a few other improvements.
Win-Installis an installer containing both Qt5 and Qt6 versions of Open Cloud Tools.
Win-Qt6is the build users of Windows 10 and newer should use.
Win-Qt5is the build users of Windows 7 and 8 should use.
Macsupports recent versions of MacOS but I’m not actually sure which. To use the Mac version you must runxattr -cr /Applications/OpenCloudTools.appin the terminal after installing to make it runnable.Big features:
- Added support for creating, incrementing, modifying, and deleting ordered datastore entries.
- Added button to automatically fetch universe name based on ID.
Changes:
- Fixed failure to list contents of ordered datastores after the API changed.
- Fixed being unable to rename API keys.
- Added more tooltips to explain functionality.
- Improved ‘in progress’ messaging for most API calls.
- Miscellaneous UI cleanup.
Distribution changes:
- Qt 5 upgraded to 5.15.14
- Qt 6 upgraded to 6.6.3
when are you planning on adding memory store service support?
Working on it now but I’m not sure how long exactly it will take. Right now my attention is split between that and re-working the interface to be less cluttered with the increasing number of APIs that are being added.
Not sure which will be ready first, but I’d guess probably a few weeks until I can release a version with memory store support.
Excited for this!
Will the interface have a major change, Or small changes?
First I should say that this ended up taking longer than I expected so I’ve switched over to working on Memory Store support first, so there will still be a memorystore-compatible version with the older interface. Hopefully will be ready in no more than a week at this point.
Most of it will be staying exactly the same, the big change is that instead of having the universe drop-down on top and then tabs under it, those will both get combined into a single list on the left that lists all of your universes and the different tools available under them. The gui for each individual tab will also be separated into its own subwindow, so you can have more than one up at once.
It is still only half-implemented but here is my mspaint concept.
Edit: Should add the subwindows will also have a title that shows which universe they are for so you don’t accidentally mix them up.
Looking good! I already like the UX, but I think it could be even better with the new tweaks. 
By the way, have you seen the new Open Cloud update? You can read more about the devforum post here.
With this update, it’s now possible to create Data Store snapshots. The new CreateUniverseSnapshot endpoint is available on Open Cloud, and you can find the details in the documentation here.
Could this be integrated of somesort inside the tool?
I’ll look at getting that into the next release, looks like it should be pretty easy to add.
My current plan is:
Latest release: Release Release 2024.08.11 · jlwitthuhn/OpenCloudTools · GitHub
This release brings partial support for Memory Store Sorted Maps, read-only for now. More will come in the next version.
Changelog:
Big features:
- Added support for reading from a memory store sorted map. More memory store functionality will be coming in the future.
Changes:
- Increased default window size to better support the amount of data available in memory stores.
Hey is there any news on the update? 
New release today, but the only new feature is Datastore snapshotting. This one also has an important fix for a mac-only bug that made it impossible to close some dialogs.
Win-Installis an installer containing both Qt5 and Qt6 versions of Open Cloud Tools.
Win-Qt6is the build users of Windows 10 and newer should use.
Win-Qt5is the build users of Windows 7 and 8 should use.
Macsupports recent versions of MacOS but I’m not actually sure which. To use the Mac version you must runxattr -cr /Applications/OpenCloudTools.appin the terminal after installing to make it runnable.Features:
- Added support for datastore snapshots.
Bug fixes:
- Fixed some dialogs that were impossible to close on MacOS.
- Several internal changes to better support the upcoming new GUI.
Next priorities for me are still more memory store stuff and the new gui. Not sure when I’ll have it done, though.
Hey, is the bulk data download supposed to save the file as a .sqlite3? i need this data to transfer over to firebase and i don’t know how to convert it.
I see it looks like you got an answer in that other thread. I would also recommend the python interface if you want to manipulate the format of that data. I don’t know exactly what firebase expects so I can’t help you too much there.
If you’re feeling more adventurous you can also build sqlite yourself and use the C API but python would be much simpler since sqlite support is already built-in.
Can I use this plugin to download a full game’s Datastore and save it to my disk as backup, and whenever I need to retrieve it, upload it to roblox?
I support this idea. It would also be really cool if we could do actions on entire data stores such as deleting all entries.
Yes, you can! You can also delete all entries, as @FlikterIsLinked mentioned he wanted to do. It’s just gonna take very very long if you have 1000+ entries lol.
Hi! Thank you so much for this. I’d also like to ask if there’s a way to bulk download datastores with specific names? For example, I want to download datastores that includes the name “PlayerInventory” only. I don’t want to download everything that I do not need. I would like to know if that’s possible at the moment. Thanks!
As you can see, I am using datastore2 so there would be lots of datastores. I don’t want to download all entries that has the word “PlayerEquippedItems”. The numbers you see are the player’s user ID and I can’t hide it manually because there’s a lot. Please help. 
