Issue with uploading to default BIM Docs project files folder using BIM 360 API

[Anonymous]

Hi,
I recently got developer account access for BIM Docs and have been using it for some integrations

Everything seems to be working fine but I am unable to upload the documents to default bucket with an error code of 403 ‘Unauthorized’ 
I have made sure there is no error at code level or scope etc. I have also tested it by using custom logic as well as C# quick start forge client and both give me back same response.
I want to confirm whether this is because of limitations on free docs account? As I was also unable to create multiple projects at docs BIM and later on found out that it only allows 1 project administration in free account

Please let me know how to solve API permission issue for uploading file and again its not issue with scope or other code error.

[Anonymous]

Hi,
I recently got developer account access for BIM Docs and have been using it for some integrations

Everything seems to be working fine but I am unable to upload the documents to default bucket with an error code of 403 ‘Unauthorized’ 
I have made sure there is no error at code level or scope etc. I have also tested it by using custom logic as well as C# quick start forge client and both give me back same response.
I want to confirm whether this is because of limitations on free docs account? As I was also unable to create multiple projects at docs BIM and later on found out that it only allows 1 project administration in free account

Please let me know how to solve API permission issue for uploading file and again its not issue with scope or other code error.

[mikako_harada]

Hi Faisal, 

Do you have API access activated for Docs? 

https://fieldofviewblog.wordpress.com/2017/08/31/bim-360-docs-account-for-development/

https://fieldofviewblog.wordpress.com/2017/01/19/bim-360-activating-api-access-to-docs/

Without it, you cannot access Docs with API.

Could you make sure about it to start with?  

Then, here is some pointer about uploading:  

https://fieldofviewblog.wordpress.com/2017/02/07/bim-360-docs-api-update/

[mikako_harada]

Hi Faisal, 

Do you have API access activated for Docs? 

https://fieldofviewblog.wordpress.com/2017/08/31/bim-360-docs-account-for-development/

https://fieldofviewblog.wordpress.com/2017/01/19/bim-360-activating-api-access-to-docs/

Without it, you cannot access Docs with API.

Could you make sure about it to start with?  

Then, here is some pointer about uploading:  

https://fieldofviewblog.wordpress.com/2017/02/07/bim-360-docs-api-update/

[Anonymous]

Hi,
I do have docs API Access for docs via forge application 
And i am able to call for documents etc. and also can create storage object as described in upload documents.
The issue is i created the storage object and uploaded a file and it gave me back success response but i was not able to view it on my BIM 360 docs account.
So i copied the storage id of another document that was already visible under my account and tried to upload file to that storage instead of creating new one but that returned a 403 error.
I guess we can not update default project buckets such as Project Files folder via API?
If so where can i view my uploaded documents taht are uploaded to new bucket?
thanks

[Anonymous]

Hi,
I do have docs API Access for docs via forge application 
And i am able to call for documents etc. and also can create storage object as described in upload documents.
The issue is i created the storage object and uploaded a file and it gave me back success response but i was not able to view it on my BIM 360 docs account.
So i copied the storage id of another document that was already visible under my account and tried to upload file to that storage instead of creating new one but that returned a 403 error.
I guess we can not update default project buckets such as Project Files folder via API?
If so where can i view my uploaded documents taht are uploaded to new bucket?
thanks

[mikako_harada]

Hi Faisal, 

I'm not quite sure what you are trying to do.  If you are uploading a file to Docs, you don't need to create your own bucket.  You will be uploading within Autodesk's product bucket, i.e., bucket key is wip.dm.prod

Did you follow the instruction I pointed earlier? There are subtle difference you may want to be aware.      

https://fieldofviewblog.wordpress.com/2017/02/07/bim-360-docs-api-update/

https://developer.autodesk.com/en/docs/data/v2/tutorials/upload-file/

• In step 5 of the tutorial, you will need to use *:autodedsk.bim360:File instead of *:autodesk.core:File.

• In BIM 360 Docs, most users have no access to the root folder which is also not visible in the UI. You have to use the topFoldersrelationship to get hold of the highest folders the caller has access to.

• You can upload any file type to any folder. If you upload supported file types to the Plans folder (including rvt and pdf), then it will automatically create Documents. These appear as review documents inside Docs. They still need manual review in Docs (e.g. to check the OCR process or text extraction worked correctly) before they are generally accessible.

[mikako_harada]

Hi Faisal, 

I'm not quite sure what you are trying to do.  If you are uploading a file to Docs, you don't need to create your own bucket.  You will be uploading within Autodesk's product bucket, i.e., bucket key is wip.dm.prod

Did you follow the instruction I pointed earlier? There are subtle difference you may want to be aware.      

https://fieldofviewblog.wordpress.com/2017/02/07/bim-360-docs-api-update/

https://developer.autodesk.com/en/docs/data/v2/tutorials/upload-file/

• In step 5 of the tutorial, you will need to use *:autodedsk.bim360:File instead of *:autodesk.core:File.

• In BIM 360 Docs, most users have no access to the root folder which is also not visible in the UI. You have to use the topFoldersrelationship to get hold of the highest folders the caller has access to.

• You can upload any file type to any folder. If you upload supported file types to the Plans folder (including rvt and pdf), then it will automatically create Documents. These appear as review documents inside Docs. They still need manual review in Docs (e.g. to check the OCR process or text extraction worked correctly) before they are generally accessible.