DB-Des Dropboxer

Hi @"eappsiadvancenow123", It would appear as though the payload request you are sending to the API is not being formed properly. Could you please share a full code snippet of the code being used to generate the payload request? As well as the language, SDK, or library being used to generate and send the request.

@"MatthiD", I'm glad to hear you were able to find a solution for your use case. To clarify, there are different types of 429 errors. It is always recommended to log the error message that accompanies an error code to get a better idea of what may be happening with the request. To help avoid a potential lock contention…

Hi @"MatthiD" You can definitely just start an upload session and then finish it, without needing to use `filesUploadSessionAppendV2`. Looking at the code snippet provided, it looks like you are starting an upload session by calling `filesUploadSessionStart()`, but are attempting to finish that same session by calling…

Hi @"jon9park" Please reach out to our support teams so that your case can be further reviewed. https://www.dropbox.com/support

HI @"kakukogou4" While we strive to provide consistent support across our API, not all endpoints are guaranteed to support the Dropbox-API-Select-Admin header, but I'll pass this feedback along as a feature request. I can't promise if or when that might be implemented though.

Hi @"rostyslavpopov" If the Client ID is a required parameter for the endpoint(s) you are using, it must be included to ensure proper functionality. Including the Client ID in your requests is both standard practice and safe. The Dropbox Sign API is designed with robust security measures in place to protect data and ensure…

Hi @"rostyslavpopov" It appears as though the JSON serialization process in your code is producing an unexpected result — the List<String> is somehow being serialized into a JSON object rather than a JSON array, which is what the API expects. We would recommend reviewing your code to ensure the template IDs are being sent…

Hi @"cas_rds", A team folder can be created by sending a request to /team/team_folder/create. Keep in mind that once that folder has been created, it will not be visible to team members until members are added to the folder itself. To add members to the folder, you will need to use /sharing/add_folder_member. To add the…

Hi @"nsalex", Since you are using the rootNamespaceId, we recommend using { '.tag': 'root', 'root': rootNamespaceId } instead of { '.tag': 'namespace_id', namespace_id: rootNamespaceId } in your request. This aligns with the naming structure and value expected by the API, thus ensuring correct functionality.

@"adsalguero", Thank you for clarifying. The value stored in the "user_within_team_space_used_cached" property should match the value in the "Usage (in MB, updates every 8 hours)" column.

Hi @"adsalguero", I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Could you clarify what you mean by "But I only get "Data (MB) member has access to"? Just to confirm, the /users/get_space_usage endpoint returns only "used" and "allocated" space when the user…

Hi @"Standa Fy", Just wanted to provide you with an update. After thorough testing, we were able to replicate the issue have described. However, it appears that the problem is isolated to the Chrome browser. During our tests, we found that the issue could not be reproduced in other browsers, such as Safari and Firefox,…

Hi @"Standa Fy", Could you also confirm that you have added the respective domain(s) for the app you are using in the app's "Chooser / Saver / Embedder domains" field, from within the App Console?

Hi @"josuegomes", Please ensure you are using an access token for the account where the backups are stored. If you are traversing the files and folders of the corresponding account, using /files/list_folder[continue] until has_more is false, the back up folder(s) should be included in the response. Typically, the folder…

Hi @"Standa Fy", Your app does not appear to be saving the App key that is entered in the app-key field. You can confirm in the Network tab of the Developer Console that, even though the call to /dropins/embed is successful (200), the value of the app_key parameter is set to undefined.

Hi @"adamb924", I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with: - the name and version number of the platform and SDK/library you are using, if any - the steps to reproduce the issue, including relevant code snippet(s), but don't include any…

@"anil6", I'm sorry to hear you are still having troubles. Could you please submit a support ticket so a member of our support team can further look into this issue for you?

@"anil6", those files would actually be located in a "HelloSign" folder, which you can find when you click on "All Files" in the sidebar, on the left. The "top" path for that folder would be /hellosign. Hope this adds further clarification.

Hi @"anil6" , If you did not provide a specific folder to save those files into when the signature requests were created, then they would have been automatically saved on your home folder. In order to move those files to a different location, you can first retrieve the document's path by making an API request to…

Hi @"candelacorpacci", In order to see the folder of an app with "Permission type: App folder" within a user's Dropbox account, the user would need to go through the authorization flow. Meaning, the user needs to authorize the app first. Once authorization has been successful, the app's folder will be visible in that…

Hi @"schrettinger", Thanks for writing in. I'll pass your suggestion along as a feature request. I can't promise if or when that might be implemented though.

Hi @"Ghislain Sommervogel", Only team admins are able to authorize apps with team scopes enabled. If you want to allow non-admins to connect to an app with team scopes enabled, you can request individual-only scopes by adding the necessary scopes in the scope parameter when constructing the Authorization URL.…

Hi @"Borrow", The "couldn't resolve hostname" error typically indicates an issue with DNS resolution rather than a problem with our API. To troubleshoot this in your application, we would recommend verifying that the hostname is correctly specified in your code and checking the use of other functions. Additionally, ensure…

Hi @"agarrkoch", Since the file corruption you are reporting is happening intermittently, we would recommend adding a validation step in your app to confirm that the local copy of a file has the same contents as the copy of the file on Dropbox. This can be achieved by using the "content hash". You can retrieve the content…

@"BruceVWilcox", file permissions are controlled by the user locally. Once the Dropbox app is installed and syncing is allowed, that user should have access to the contents of that Dropbox folder. Have you confirmed the file or folder you are attempting to access exists with directory.exists() function in your Java script?

Hi @"Tomzr", There are no additional actions that need to be taken when sending a request to /files/get_temporary_link to generate a temporary link. Since you have confirmed only some users get the error message, it could very well be security software blocking connection to the domain contained in the link. Feel free to…

@"Jagan Tirumalai", the example of the PKCE auth flow is meant to serve as a reference implementation. It's designed to help developers understand how PKCE works in practice but may not be suitable for all use cases or production environments without modification. We recommend reviewing the code and adapting it to fit your…

Hi @"BruceVWilcox", The local Dropbox folder should be readable. The issue you are encountering is most likely a local permissions issue. Since the behavior you are describing is not an error from the Dropbox API itself, we can't offer much more help with that in particular.

@"bossgolfer", It is recommended to get an access token via an OAuth flow, yes. Keep in mind that access tokens, whether obtained from the app within the App Console or via OAuth flow, will eventually expire. The expiration time can be confirmed in the property expires_in, which is found in the response object returned…

Hi @"bossgolfer", A 'missing_scope' error indicates that while the app may be permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to…