Greg-DB Dropbox Community Moderator

Even if you don't have many files in your account, it's possible the list_folder and list_folder/continue results will be paginated, so you should make sure your app is always checking has_more and calling back if it's true. If the API isn't working as expected though, please share the API calls an unexpected output so we…

When calling list_folder, you need to check the has_more value in the response. If it's true, you need to call back to list_folder/continue with the last returned cursor to get more results. You can find more information on how this works in the documentation for list_folder:…

If you have a shared link for the file, the simplest way to download it is to modify the URL parameter(s) as shown here: https://www.dropbox.com/help/desktop-web/force-download You can then download from the modified link. Otherwise, if you do want to use the API, you can use the /2/sharing/get_shared_link_file endpoint:…

No, unfortunately there isn't a good solution here. The filesListFolder call will only return the newly uploaded file once it finishes uploading. The API doesn't offer information on uploads that are in progress. I'll send this along as a feature request for a way to receive progress information for uploads.

I don't have an update on this feature request right now. Note that we actually just announced a general extension for access to API v1 though, until 9/28/2017: https://blogs.dropbox.com/developers/2017/06/updated-api-v1-deprecation-timeline/

We looked into this, and we believe the issue here is due to this possible behavior from Stream.Read: Return Value Type: System.Int32 The total number of bytes read into the buffer. This can be less than the number of bytes requested if that many bytes are not currently available, or zero (0) if the end of the stream has…

To acknowledge the deprecation, sign in to the account that owns the API app and go to the App Console: https://www.dropbox.com/developers/apps There will be a banner there asking you to acknowledge it, if you haven't already. (There's a decent change you have already, since the emails we sent out last year and this year…

@"perholmes" We actually just announced a general extension for access to API v1, until 9/28/2017: https://blogs.dropbox.com/developers/2017/06/updated-api-v1-deprecation-timeline/ Hope this helps! 

Dropbox propose une API que vous pouvez utiliser pour télécharger et télécharger des fichiers par programme. Vous pouvez trouver tout ce dont vous avez besoin pour commencer avec l'API Dropbox, y compris la documentation, les didacticiels et les SDK ici: https://www.dropbox.com/developers L'utilisateur doit autoriser…

Thanks for the additional feedback! It is helpful.

For reference, this JavaScript SDK auth example shows how to initiate the app authorization flow: https://github.com/dropbox/dropbox-sdk-js/blob/master/examples/javascript/auth/index.html#L89 The parameter passed to getAuthenticationUrl should be where the user should be sent back to after authorizing your app. In your…

Thanks for trying that. I did find this issue on the requests GitHub that indicates this should be fixed in 2.18.1 though: https://github.com/requests/requests/issues/4160 Can you try adding the print statement in dropbox.py directly (i.e., our library, not your dbox.py) to see if it's somehow picking up a different…

No, it's not possible to retrieve the app owner's account information from an app key and secret.

API v1 and API v2 offer entirely different interfaces, so you will need to update how your app integrates with Dropbox by making changes to your app's code. To use API v2, we recommend using one of the official SDKs, if possible. We don't have an SDK for PhoneGap in particular though:…

Once API v1 is retired, any further API v1 calls will fail with a 400 error with the body: {"error": "v1_retired"} This would be translated to a native error type in the SDKs. So, if users try to access Dropbox functionality via API v1 after it is retired, that functionality will not work. The exact user experience will…

When using the OAuth 2 "token" flow, only the app key is necessary and the app secret isn't used. In the "code" flow, both the app key and secret are necessary. You can find more information on the different OAuth 2 flows in the documentation here:…

The documentation for this method can be found here: https://dropbox.github.io/dropbox-sdk-obj-c/api-docs/latest/Classes/DBFILESUserAuthRoutes.html#/c:objc(cs)DBFILESUserAuthRoutes(im)uploadData:mode:autorename:clientModified:mute:inputData: From there, the first parameter (which is unnamed in the calling code) is the…

(I was writing this in response to your new messages, but it looks like you either deleted them or there's an issue with the forum not displaying them.) The 'path/not_found' error indicates that there's nothing at the path you specified. When referencing paths in Dropbox, you should use the remote path, not the local path…

I can reproduce this with requests==2.18.0, but not requests==2.18.1. Can you double check that 2.18.1 is actually getting used, and not 2.18.0? E.g., try doing this right before the API call, like you're doing with the Dropbox library: import requests print(requests.__version__)

The ListFolderResult.entries array contains Metadata objects. These can represent files, folders, or deleted items. The entry would be a FileMetadata, FolderMetadata, or DeletedMetadata, respectively. These are all subclasses of Metadata, but size is only available on FileMetadata. So, you should do something like this:…

The Dropbox API doesn't offer this unfortunately, but I'll be sure to pass this along as feedback. (The closest thing is the file templates/properties functionality, currently in preview, but that's only available for Dropbox Business teams/apps.)

Yes, while any further API v1 calls will fail once API v1 is retired, there's no requirement for users to begin calling API v2 before that. They can begin calling API v2 at any time, and existing access tokens will still be active.

Yes, you should use files_list_folder and files_list_folder_continue to list the contents of any folder, including root. The root path is identified by the empty string "".

Can you share the full HTTP request/response for the call with the unexpected 201 response so we can investigate? Just be sure to redact the access token. (Feel free to open a ticket instead if you'd prefer to share privately: https://www.dropbox.com/developers/contact ) Thanks in advance!

This secondary issue should also be fixed now.

The SwiftyDropbox library runs API requests for these methods asynchronously. That is, when you call client.files.upload, that method will return before the API request itself completes. So, to limit how many are running at once, you need control how many times you call client.files.upload to begin with. You can't just run…

Apologies for the confusion. The curl example in the documentation and API Explorer for /2/auth/token/from_oauth1 are unfortunately incorrect. I'll let the team know to fix that. That endpoint actually uses app authentication ( https://www.dropbox.com/developers/reference/auth-types#app ), so a bearer access token isn't…

According to the documentation, we only support the "bearer" token type, so any of these should be fine.

Apologies, my reply was a little misleading. It seems CURLOPT_WRITEFUNCTION doesn't return a stream object exactly, but it's a way for you to supply a function that will be called multiple times to read data off the reply a piece at a time. In any case, this is more about using curl in PHP now, which is outside my area of…

The file data is returned in the HTTP response, so you could read from it as a stream if your HTTP client supports it. It looks like PHP curl's may effectively support this via CURLOPT_WRITEFUNCTION: http://docs.php.net/function.curl-setopt