You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Is it possible to set client_modified when uplading files using /upload_session?
Hello,
I am currently attempting to add a feature to our software that sets the client_modified date on every file we upload. This is easily done when uploading files through the /upload route. However, this route does not allow files larger than 150 MB. For those large files, I'm using the /upload_session endpoints, but these endpoints don't seem to support setting client_modified. Modifying client_modified also doesn't seem to be possible outside of uploading.
Is there any way to set client_modified on files larger than 150 MB? Thanks!
Yes, when using upload sessions, you can set the 'client_modified' when you commit the file via /2/files/upload_session/finish using the 'commit.client_modified' parameter. (Likewise, if you're using /2/files/upload_session/finish_batch, it's the corresponding 'entries.commit.client_modified'.) You can click on the types, e.g., `CommitInfo`, in the documentation to expand them for more information.
- Greg-DB
Dropbox Staff
Yes, when using upload sessions, you can set the 'client_modified' when you commit the file via /2/files/upload_session/finish using the 'commit.client_modified' parameter. (Likewise, if you're using /2/files/upload_session/finish_batch, it's the corresponding 'entries.commit.client_modified'.) You can click on the types, e.g., `CommitInfo`, in the documentation to expand them for more information.
Thank you, Greg. That did work for me. I was trying to put the client_modified at the top level of the parameters to /upload_session/finish, as we do with /upload, rather in commit.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
