Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
sharing/get_file_metadata fails for admin
Hi
I tried to call sharing/got_file_metadata with the admin id, and with "Dropbox-API-Select-Admin".
It failed and returned "invalid_file"
When I use the same file id with it's owner id, it wor...
Oh yes you are right, I looked at "get_metadata" which is has a whole team permission (Is there a reason for the inconsistenty of those permissions?).
But now I have the following problem:
#!/usr/bin/env python3
import requests
import json
from pprint import pprint
URL_FOLDER = 'https://api.dropboxapi.com/2/sharing/get_folder_metadata'
URL_FILE = 'https://api.dropboxapi.com/2/files/get_metadata'
TOKEN = '***-****'
FILE_ID = 'id:'
ADMIN_ID = 'dbmid:'
def do_request_file(member_id):
headers = {
"Authorization": f"Bearer {TOKEN}",
"Content-Type": "application/json",
"Dropbox-API-Select-Admin": member_id,
}
params = {
"path": FILE_ID
}
r = requests.post(URL_FILE, data=json.dumps(params), headers=headers).text
return json.loads(r)
def do_request_folder(member_id, folder_id):
headers = {
"Authorization": f"Bearer {TOKEN}",
"Content-Type": "application/json",
"Dropbox-API-Select-Admin": member_id,
}
params = {
"shared_folder_id": folder_id
}
r = requests.post(URL_FOLDER, data=json.dumps(params), headers=headers).text
return json.loads(r)
metadata = do_request_file(ADMIN_ID)
pprint(metadata)
pprint(do_request_folder(ADMIN_ID, metadata["sharing_info"]["parent_shared_folder_id"]))returns:
{'.tag': 'file',
'client_modified': '2019-09-05T09:12:38Z',
'content_hash': 'ccae535b5ac41d418b23187d9517ba652361bb9463e6b39e66f4e315bb21c910',
'id': 'id:*******',
'is_downloadable': True,
'name': 'File2.pptx',
'parent_shared_folder_id': '6201828192',
'rev': '******',
'server_modified': '2019-09-05T09:12:38Z',
'sharing_info': {'modified_by': 'dbid:*****',
'parent_shared_folder_id': '6201828192',
'read_only': False},
'size': 29445}
{'error': {'.tag': 'invalid_id'},
'error_summary': 'invalid_id/.',
'user_message': {'locale': 'en', 'text': 'Invalid shared folder ID.'}}Even though team admin is accessible to folders
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThanks for following up, and apologies for the confusion. Looking at this, I believe you're running in to a particular edge case, where the field names can be misleading.
The file for which you're getting the metadata in the first call is actually in a (different member's) home namespace, not a shared folder. Due to some implementation details though, that user's home namespace information is being returned in the file metadata as if it were a shared folder.
Then, the sharing endpoint in the second call is rejecting the ID since it's not technically a shared folder ID.
If you want to get the metadata for that parent folder, you can do so by calling /2/files/get_metadata for that namespace under that team's root namespace. Here's what that would look like in this particular case, in curl:
curl -X POST https://api.dropboxapi.com/2/files/get_metadata \
--header "Authorization: Bearer TOKEN_HERE" \
--header "Dropbox-API-Select-Admin: ADMIN_ID_HERE" \
--header "Content-Type: application/json" \
--header 'Dropbox-API-Path-Root: {".tag": "root", "root": "TEAM_SPACE_ROOT_ID_HERE"}' \
--data "{\"path\": \"ns:6201828192\"}"
Check out the Namespace Guide for more information on how this works, and for information on how to get the team space root ID and how to use the 'Dropbox-API-Path-Root' header.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
