We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.
Forum Discussion
Dropbox API error with 500
Greetings, I am encountering the following error while calling the Dropbox API: InternalServerError('6c7329b49922471380831b2b3f2fb49c', 500, '{"error": "The server has either erred or is inca...
Yes, that error indicates an issue with the value passed to as_user. The as_user method requires a team member ID, not an email address. You can get team member IDs from team_members_get_info_v2 or team_members_list_v2 and team_members_list_continue_v2, for example.
You're right! there's some whitespace in our token string. thank you for your help.
After removing the whitespace, we've encounter an error below:
('feefc7a078c647338e0c5381bc129ff8', 400, 'Error in call to API function "users/get_current_account": Invalid select user id format')
('61bd222a697c4c4586ec7954d87ae3bb', 400, 'Error in call to API function "users/get_current_account": Invalid select user id format')
('e809c790be5a4994a0612d593f8b1be5', 400, 'Error in call to API function "users/get_current_account": Invalid select user id format')
('89e8b8eb91904084824fb114ae56eaa3', 400, 'Error in call to API function "users/get_current_account": Invalid select user id format')
Here is the latest version of the code we are currently using:
some_id = 'example@pping.kr'
self.dbx = dropbox.DropboxTeam(self.app_token).as_user(some_id)
root_namespace_id = self.dbx.users_get_current_account().root_info.root_namespace_id
self.dbx.with_path_root(dropbox.common.PathRoot.root(root_namespace_id)).files_list_folder(path)
Is there a mistake while using user_id?
Greg-DB
Dropbox Staff
Dropbox StaffYes, that error indicates an issue with the value passed to as_user. The as_user method requires a team member ID, not an email address. You can get team member IDs from team_members_get_info_v2 or team_members_list_v2 and team_members_list_continue_v2, for example.
It works. Thank you!
Yet we have another issue with the refresh token, but we will ask about this in another thread next time.
Thank you again.
