The authorization code supplied in the API request is missing or no longer valid. Verify the authorization code is set correctly in your request, or your application likely needs to get a new authorization code. The item.type field of the collaboration item should be set to folder. Item type must be specified and set to 'folder' Change the folder ID for the folder move request.ĭelete all content from the folder before attempting to delete it. The folder ID specified in the folder move would create a cyclical folder structure (for example moving a folder to a subfolder within itself). Use a different folder ID than the root folder.įolder move creates cyclical folder structure You cannot set collaborators on a user's root folder (folder ID 0). Specify the ID of the user that the content should be transferred to by setting the owned_by.id field in the request.Ĭollaborations_not_available_on_root_folder Check the extended error message in the response body for more details.Ĭannot_make_collaborated_subfolder_privateĬannot move a collaborated subfolder to a private folder unless the new owner is explicitly specified. Required parameters supplied in the API request are either missing or invalid. Supply a valid SHA-1 hash of the uploaded file. The SHA-1 hash that was supplied in the request did not match what was received in the upload. While uploading a file, a content-md5 header with the SHA-1 hash of the file can be supplied to ensure that the file is not corrupted in transit. The specified content-md5 did not match what we received.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |