Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
How to Programmatically Get a List of All Registered Apps and Their Permissions?
Hi — in the Dropbox web UI I can see registered apps ( permissions / scopes they have). I can’t find an API endpoint to fetch that same list. Is there a documented API (or other programmatic method) to retrieve all registered apps and the scopes/permissions they hold? I’ve checked the standard Dropbox API docs but didn’t spot this. Any pointers, sample endpoints, or workaround (e.g., admin/team endpoints) would be helpful. Thanks!
Scoped access within shared environment
Hey Dropbox team, I have tried to find how to approach this but can't seem to get a clear answer. Our situation: Shared dropbox directory with 5 members. These members should have access to the outputs from some automation tools. (Github actions produces .exe which gets uploaded to dropbox for all members to enyoy). Now i would like for my automation tool to only have access to the /AutomationOutputs/ directory as the rest of the drive is filled with important data which we do not want to lose. I could program my automations in a way where they never thread out of the AutomationOutputs/ directory, but I would prefer to limit the scope for the tool itself so that could never happen. What would be the suggested approach for this situation? With kind regards, Joppe
Eternal "in_progress" in "check_job_status" ?
Hi there! After creating the file transfer task, I did not get a status other than "in_progress". I checked for 10 minutes, the result is the same. https://api.dropboxapi.com/2/files/save_url Headers: Dropbox-API-Path-Root:{".tag":"root","root":"***11017011"} Content-Type:application/json Body: { "path": "/TrueCare24/Getting started.pdf", "url": "https://cdn.filestackcontent.com/4HanfOIvSVW4gHeOUbm9" } Response: { ".tag": "async_job_id", "async_job_id": "SPaPOLIucOYAAAAAAAAAAQ" } https://api.dropboxapi.com/2/files/save_url/check_job_status Headers: Dropbox-API-Path-Root:{".tag":"root","root":"***11017011"} Content-Type:application/json Body: { "async_job_id": "SPaPOLIucOYAAAAAAAAAAQ" } Response: { ".tag": "in_progress" } There are no problems with other files. I have transferred many thousands of files and everything is ok. TrueCare24 is Team Folder
May timeouts when calling get_current_account endpoint
We’ve noticed a recent surge in errors reported by some users of our app when calling the get_current_account endpoint. Specifically, the requests are timing out, which is unusual because we haven't had any issues and our code has not changed. This issue started occurring last week and seems to be affecting users mainly in Canada. Could you help us understand if there are any known issues on Dropbox’s side, or if there have been recent changes to the API that could be causing these timeouts? Thanks in advance for your assistance! Regards, EnriqueSingle API call creating duplicate file versions using Dropbox .Net Api
Hi Dropbox Support, I'm experiencing an issue with the Dropbox .NET API where a single file upload API call is creating two identical versions of the same file with the following problems: Problem details: Using Dropbox .NET API for file uploads One API request results in two file versions created 1ms apart Different attribution: One version shows "edited by user on web", the other shows "edited by user on API app" All uploads are done through API only - no web interface involvement This happens inconsistently - some files upload normally, others create duplicates API methods used: For small files: uploadArg = gcnew Dropbox::Api::Files::UploadArg(dropboxPath, Dropbox::Api::Files::WriteMode::Overwrite::Instance, false, clientModified, true, nullptr, false, nullptr); uploadTask = m_dropboxclient->Files->UploadAsync(uploadArg, fileStream); For large files: task = m_dropboxclient->Files->UploadSessionFinishAsync(cursor, commitInfo, nullptr, fileChunk);
This app is not valid when trying to authenticate with Oauth
I'm trying to connect Salesforce to Dropbox and I've created an app on Dropbox. I've set up the Auth provider and have a URI redirect setup, but no matter if I use the actual URI or localhost, I always get the "This app is not valid" error message. I went so far as to build the URL manually to connect : https://www.dropbox.com/oauth2/authorize?response_type=code&scope=files.content.write+file_requests.write&state=12345&client_id=clientID&redirect_uri=http://localhost I've verified the App key as the client id several times and it's correct. I've tried using a browser in incognito mode. I've tried re-creating the app from scratch and doing it all again. The status of the app is Development, but that seems correct, as I'm just trying to connect to it myself. Any obvious issues?files/search_v2 400 error
I'm new to Dropbox API. I'm trying to use files/search_v2 API and got a 400 error with a bearer token created by My Apps in my developer console. I'm trying to access files in my Team's folders. I've tried the following: 1. When I use the access token generated by Dropbox API Explorer, that works. 2. When I use the same CURL command by replacing the bearer token generated by My Apps, it's not working and got the HTTP 400 error. curl -X POST https://api.dropboxapi.com/2/files/search_v2 \ --header "Authorization: Bearer $TOKEN" \ --header 'Content-Type: application/json' \ --data '{"query":"test"}' 3. When I use the same bearer token generated by My Apps with another Dropbox API, such as team/get_info, it works. 4. That makes me wonder if I need to include all the read scopes in my app. I tested with all the read scopes in both User and Teams scopes, but (2) still didn't work. I'm trying to make (2) work with My App. Any clues/tips/guidance are greatly appreciated!Invalid shared folder ID when trying to mount
Hi! I have a shared link from account A pointing to a folder that I'm trying to mount in account B using the dropbox node SDK. This is what I'm doing: Get folder ID for shared link: client.sharingGetSharedLinkMetadata({url: sharedFolderUrl}) This gives me an ID (ns:{identifier}) 2. Mount shared folder: client.sharingMountFolder({shared_folder_id: 'ns:{identifier}'}) }) I expected this to do the equivalent of accepting the request to join a folder but this gives me the attached error. Any idea why?
