![]() This error is typically produced when scopes that are needed for the API operation are not enabled. The request requires higher privileges than provided by the access token. The Access Token does not have the appropriate user permissions or scopes. The user that you are attempting to collaborate in on an item is already collaborated on that item. The user will need to accept the terms of service, or the admin will have to disable them, in order to proceed. The admin of your Box account has set custom terms of service and the user has not logged in to accept the terms yet. User must accept custom terms of service before action can be taken ![]() Adjust the user permissions to allow the assignment of tasks. The user who is attempting to assign the task does not have the appropriate permissions to do so. A possible solution is to set the sync_state of the item to not_synced.Īssigner does not have sufficient privileges to assign task to assignee The item is set to be synced by the Box sync clients and cannot be moved. See the reference docs for the API operation for available format sizes. The thumbnail size requested for the file is not valid. Adjust the bounds to fit within the size of the item and try again. The range header supplied does not fit within the size of the specified item. Requested representation page out of range The user has not yet completed account setup steps. Include the file metadata before the file's contents. Metadata is included after file contents in a file upload request. The maximum length of a file or folder name in Box is 255 characters or less. Shorten the length of the name that is being supplied for the item. File names containing non-printable characters, names containing the characters /, \,, :, ` Box only supports file or folder names that are 255 characters or less. Use the same session ID from the session that was created. The session ID supplied when making a chunked upload API request was invalid. The upload session ID provided in the URL is not of a valid format. The status of a collaboration can only be updated to accepted or rejected by the user specified in the accessible_by field when the current status is set to pending. You can change the status only if the collaboration is pending Check the API reference documentation for the correct request parameters that should be supplied for the API operation. Invalid parameters were sent in the API request. To fix this error, update the Unix time on your machine to match a synchronized time server, then try the request again.Īdd a valid numeric value for the supplied limit value.Īdd a valid numeric value for the supplied offset value. ![]() This error occurs when the Unix time on your local machine and the Box server are out of sync. Attempt to refresh the access token or fetch a new one.Ĭurrent date time must be before the expiration date time listed in the 'exp' claim. If correctly set, the access token may have expired. Possible solutions are to verify that the access token is added correctly in the request. 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 |