Paid plan: Does it unlock file upload to 3D storage API?

Aspose.3D Cloud Product Family
1

Hello Aspose Support Team,

Thank you for your quick response!

PROJECT CONTEXT:
I’m developing a Chrome extension called “Drive 3D Viewer” that allows users to
visualize 3D files directly from Google Drive, including Blender files (.blend).

THE CHALLENGE:
Since browsers cannot natively display .blend files, I need to convert them to GLB
format first. That’s why I’m using the Aspose.3D Cloud API.

WORKFLOW:

  1. User selects a .blend file from their Google Drive
  2. Extension downloads the .blend file (2.8 MB in my test case)
  3. Upload to Aspose.3D Cloud Storage (InternalStorage)
  4. Convert .blend → .glb using the conversion API
  5. Download the converted .glb file
  6. Display in a Three.js-based 3D viewer

THE ISSUE:
I was getting a 401 “Authentication failed!” error when trying to upload files
to storage, even though my OAuth token was valid.

WHAT I’VE DONE:

  • Created InternalStorage in my dashboard
  • Updated endpoints to use /v3.0/3d/storage/file/ (API-specific, not generic)
  • Set storageName=InternalStorage parameter
  • Upgraded to a PAID plan to unlock storage upload functionality

TECHNICAL DETAILS:

  • Client ID: 3fe43104-57a1-4605-b47e-5b595fd6dd60
  • Storage: InternalStorage (retention: 24 hours)
  • Endpoints used:
    • Upload: PUT /v3.0/3d/storage/file/{fileName}?storageName=InternalStorage
    • Convert: POST /v3.0/3d/{fileName}/saveas/format?newformat=glb
    • Download: GET /v3.0/3d/storage/file/{fileName}?storageName=InternalStorage

QUESTION:
Now that I have upgraded to a paid plan, should the file upload work correctly?
Is there anything else I need to configure?

I will test now and report back with the results.

Thank you very much for your assistance!

Best regards

2

@agalliez

Upgrading to a paid plan should indeed unlock the file upload functionality to the Aspose.3D Cloud Storage. If you are encountering a “401 Authentication failed!” error, please check the following:

  1. OAuth Token: Verify that your OAuth token is valid and has the necessary permissions for file uploads.

  2. Endpoint Configuration: Ensure you are using the correct endpoint for uploading files:

    PUT /v3.0/3d/storage/file/{fileName}?storageName=InternalStorage

  3. Storage Name: Confirm that the storageName parameter is set to InternalStorage in your request.

  4. File Name: Check that the {fileName} in the URL is correctly formatted and does not contain any invalid characters.

If you have verified all these points and are still experiencing issues, consider reaching out to Aspose support for further assistance. Testing the upload again after these checks would be a prudent next step.

Good luck with your project!