Greg-DB Dropbox Community Moderator

Yes, the "logins" events apply to logging in using SSO as well. The "timestamp" on a TeamEvent is the date/time the event itself took place. So for a login, it's the time the user logged in, regardless of how long they stay logged in after that.

@"HristoYordanov" Здравко is correct. The new folders do not have a shared folder ID because they are not themselves shared folders. They instead just have a parent shared folder ID because they have a parent that is a shared folder. To manage the sharing of those folders in particular, they would need to be shared…

@"Mgymnasts" As Здравко said, a path/not_found error is not expected when calling files_list_folder with a path value of the empty string ''. Like they recommended please double check the path parameter value you're setting when making that call, and double check if that's the particular call that is resulting in that…

Yes, while the app can request a maximum number of events to return per page, in some cases the server may return fewer than that number. That means that when you send a limit of 5, it is possible that the API will return one or even zero events on any given page. This will vary depending on a number of factors on the…

Thanks for the feedback! The Dropbox API does not currently offer the ability to control the file request naming conventions, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

Thanks for following up with this additional information. We do not currently provide API support over web calls, but we can continue helping here. Looking at the information you provided, I see you're calling /2/team_log/get_events, but you didn't mention or show how you're checking the result and calling back to…

@"saharin" Can you clarify what you mean when you say "This ok"? Have you resolved this issue?

Thanks for the report! I just tried this functionality myself, and I was able to retrieve events from after 2019 using the /2/team_log/get_events[/continue] endpoints, so we'll need to look into this more specifically for you. So that we can reproduce and investigate the issue you're seeing, please reply with: * the name…

Thanks for the feedback! If you'd like to share the details of that issue with the Dropbox SDK, such as the code/steps to reproduce the issue and the full error/output you're getting, we'll be happy to take a look.

@"saharin" I just tried out that original code sample, and it worked for me. If you're still having trouble with this, can you let me know the version numbers of each of the following that you're using? * Visual Studio * .NET Framework * Dropbox .NET package

Can you clarify what you mean when you say "altough the version of Axios in both environments is the same, the user agent is different"? The "user-agent" request header value being set by the client does seem to indicate that a different version number of Axios is being used in each case.

@"ABDUL Salam" No, unfortunately the /2/files/save_url endpoint doesn't offer "write mode" options, e.g., to overwrite an existing file at the specified location, like /2/files/upload does. I'll pass this along as a feature request, but I can't promise if or when that might be implemented. 

Thanks for following up with the additional information. I see you're getting an error: TypeError: Cannot read properties of undefined (reading 'name') That's not an error from the Dropbox API itself, but rather an error indicating that your 'file' variable is undefined. You'll need to debug your code to determine why that…

Thanks for following up. The /2/files/upload endpoint supports uploading files up to 150 MB, so a 25 MB file should be fine. That being the case, it's unclear what may be causing this, so to investigate further I'd need some more information. Please reply with: * the name and version number of the platform and Dropbox…

I notice you're calling the /2/files/upload endpoint when this occurs. How big is the file you're trying to upload when it returns this error?

You can find information on /2/files/move_batch_v2, such as its possible return types, in its documentation here. If you get a async_job_id back, you should use /2/files/move_batch/check_v2 to check the status of the job. You can find the documentation for that here.

Dropbox does not provide code review or debugging services, but we can help with any specific questions or issues you have regarding the Dropbox API if you provide the details. For example, if you need help with some particular issue on the Dropbox API, reply here with the details of the issue: * the name and version…

Thanks for the detailed post! The 'development' versus 'production' status of your app affects how many accounts can be connected to your app but it doesn't affect the content types/encodings of the messages returned by the API. Does your development environment have a different version or configuration of 'axios' than…

We can't offer help with FileMaker itself, but if you're having trouble with the Dropbox API in particular, please share the relevant request and response for the problematic API call so we can take a look. Please show the actual parameter values you're sending, but be sure to redact your access token.

Dropbox does offer an API endpoint /2/files/save_url which allows you to specify a particular URL to a file and a path where you'd like to save that file in the connected Dropbox account. You can supply the public URL, and programmatically build the desired destination path in your code. By the way, that's a link to the…

From that description, it sounds like the code you're using for the "concurrent" type is sending the wrong pieces of data and/or sending the data with the wrong offsets. You'll need to debug the code you've written for that to determine why it's doing so and how to correct it.

We don't have resources for React in particular, but for integrating with the Dropbox API from JavaScript, we recommend using the official Dropbox JavaScript SDK. You can find documentation and examples for that there. Otherwise, if that SDK doesn't work for your use case, you can use the HTTPS endpoints directly (or…

Yes, the UploadSessionAppendV2Async method supports both "concurrent" and "sequential" upload session types. Which one you use is up to you, but in either case you'll need to make sure you're sending the correct data at the correct offsets.

The code you shared calls /2/files/get_metadata, which retrieves metadata for a file or folder, but if you want to delete something, you should instead call /2/files/delete_v2 (or /2/files/delete_batch to delete multiple items). In any case, to debug a 400 error like this, print out the response body. It should contain a…

I'm not sure I understand your question, but please note that we cannot provide support for Laravel, as it's not made by Dropbox. For help using Laravel, please refer to the support resources for Laravel in particular. If you have any questions or issues regarding the Dropbox API itself, please share the details of that…

Can you clarify what you mean when you say "code is fine, and doesn't have any errors"? How have you verified that the code is uploading the correct data? For instance, I don't see in this code where you're using "memStream", so it doesn't look like you're sending the actual file data. Refer to the…

@"siva s" Thanks for following up with the information. I see you're using /2/files/upload to upload files. The /2/files/upload endpoint is a "content-upload" style endpoint, meaning that it takes the raw data to upload in the request body. Dropbox does not modify the file data you supply when uploading to the Dropbox API…

@"karver" Apps with the "app folder" access type can only access the contents of the special app folder that gets automatically created for it. If your app has the "app folder" access type, then it will only be able to access files in the app folder, and the root for any path value supplied by that app will automatically…

Thanks! I don't see any other reports of this "Amsi.Edge.22.C2AFDFF1" internally or elsewhere online, and it may be a false positive, but I'm raising this with the team regardless. By the way, it's not necessary to download the SDK source to just use the SDK in your app; if you're trying to use the SDK in your app we…

@"dsoprea" I see Здравко already offered some helpful guidance, but to add a bit more information: When using only "user scopes", an app will only be linked to specific accounts, and webhooks would notify only about specific accounts. You can find the documentation for that kind of webhooks here. When using "team scopes",…