Introducing Open Cloud Assets API

Updates Announcements
#21

Will this support uploading Plugins in the future?

1 Like
#22

This API will support all asset types Roblox have eventually. So definitely Plugin will come in the future.

4 Likes
#23

no OBJ??? that’s rlly sad,.,…,.,.,.,

1 Like
#24

Would this mean that eventually this could support developer products? Because I have been waiting for open cloud to support gamepasses/developer products for a while.

#25

When do we get a groups API? This is cool but I think the groups API would be more useful.

1 Like
#26

Why no rbxm/rbxmx support?? That’s dumb.

#27

I mean, you can just drag those into studio? As opposed to having to do the whole mesh importer thing.

Looks cool, gonna automate blender

#28

It is already a feature of groups API if I am not mistaken. You just need to create the API key under the Roblox group to authenticate permission to upload to a group I believe (if you also check the docs it talks about how to select to the groups).

Please let me know if I am wrong though cuz I have not tried it but from what I can see I don’t see what is stopping it.

#29

This is a nice change, however I can only see a couple of potential use cases.

#30

Because this API is for uploading new assets. If something is an rbxm/rbxmx, then it has obviously been uploaded already.

#31

To clarify: when do we get a group rank API as well with audit logs and such, without having to rely on groups.roblox.com?

2 Likes
#32

Rojo can construct rbxm(x) files, so it seems valid to allow such types to be uploaded as models IMO

2 Likes
#33

I’m confused by asset updating docs. It says that the endpoint is /v1/assets/{assetId}, but then the cURL example doesn’t use assetId in the path, but rather as a form parameter. Which one should it be?

Doc link

Highlighting these areas:

update_asset
update_asset918×751 53.4 KB

Even more confusing is that the usage guide uses both the path param and the form param:

update_asset_2
update_asset_2909×229 20.7 KB

Also, I’m curious as to why this can’t be used to update other fields of the asset? e.g. name, description. I understand how only models can be updated in terms of actual asset data, but it would be nice to have the ability to edit any metadata too.

The request parameter is also typed as an Asset type, but that’s not true if it only takes assetId.

#34

Thank you for the feedback, Sleitnick. The example in the usage guideline is correct. We’ve pushed a fix for the API reference doc. And we are currently working on supporting the metadata update for name, description as mentioned in the announcement. When it is ready, you’ll be able to update them with the Patch assets/v1/assets/{assetId} endpoint.

2 Likes
#35

We are actively working on extending this support to more asset types, as well as adding get/update asset metadata support using the API. Stay tuned!

Would this include the asset ID?
On successful upload, I just get a path returned, which says something like operations/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Edit: Nevermind, it’s another request :man_facepalming:

1 Like
#36

It would be very impractical to upload a new model each time your project is built. Guess you’d have to put something in place so that it only re-uploads when a change is made.

#37

Has anyone managed to get this to work using Javascript/typescript?

I can get it to work with python, but I have a use case that requires JS/TS and it always gives me a 401 error

#38

What library are you using to make http requests? (i.e. node-fetch, axios, got, etc)

#39

Node-fetch through a heroku app

#40

Added support for assets in rbxcloud!

3 Likes