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
Paper API - how to query "old" paper docs with the "new" 2020 API
Hello, we're building an integration of Dropbox Paper to our service - many dropbox paper users have requested it. Seems that Dropbox Paper itself is being migrated from its own place of paper.dropb...
when a user connects Dropbox with OAuth2, we need to be able to query all their Dropbox Paper. How do we do that for legacy users who have been around before Sep 25 2019, without using the deprecated endpoints.
Right now, the only way to programmatically access Paper docs for users that haven't been migrated (i.e., not .paper files), is to use the old endpoints. While they're marked deprecated, they are still available to use for this.
Where would the .paper docs be migrated to, i.e. under which path?
I don't have specifics to share like this right now, such as the exact path(s) for migrated docs. Note that users can move around .paper files anyway though, so I don't recommend relying on them being under a particular path. You'll want to be able to handle them anywhere, e.g., by listing them using /2/files/list_folder[/continue], like you would with normal files.
How do I query for the .paper file contents? We need those to help our users with full text search functionality. The migration guide suggests /files/export but that endpoint seems deprecated.
To retrieve the content of Paper docs from .paper files, you should use /2/files/export. That's not marked deprecated though. Did you see it set as deprecated somewhere? Please let me know if so, so we can fix that up. Thanks!
Greg-DB
Dropbox Staff
Dropbox Staffwhen a user connects Dropbox with OAuth2, we need to be able to query all their Dropbox Paper. How do we do that for legacy users who have been around before Sep 25 2019, without using the deprecated endpoints.
Right now, the only way to programmatically access Paper docs for users that haven't been migrated (i.e., not .paper files), is to use the old endpoints. While they're marked deprecated, they are still available to use for this.
Where would the .paper docs be migrated to, i.e. under which path?
I don't have specifics to share like this right now, such as the exact path(s) for migrated docs. Note that users can move around .paper files anyway though, so I don't recommend relying on them being under a particular path. You'll want to be able to handle them anywhere, e.g., by listing them using /2/files/list_folder[/continue], like you would with normal files.
How do I query for the .paper file contents? We need those to help our users with full text search functionality. The migration guide suggests /files/export but that endpoint seems deprecated.
To retrieve the content of Paper docs from .paper files, you should use /2/files/export. That's not marked deprecated though. Did you see it set as deprecated somewhere? Please let me know if so, so we can fix that up. Thanks!
- Greg-DB
Quick update: we have extended the timeline for this: https://www.dropbox.com/lp/developers/reference/paper-migration-guide
Also, you can find some more information on how the migration works here: https://help.dropbox.com/files-folders/paper/paper-2020-faqs
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
