The /paper/archive endpoint will not have a Dropbox API equivalent, so you won’t be able to programmatically archive Paper docs. paper files and other online-only files in this blog post. Read more about the behavior and limitations of. paper files for any Paper docs created by a Dropbox account on or after September 25. If your app already uses the Dropbox API to fetch a user’s files, you’ll start seeing. Start using the Dropbox API to fetch Paper docs that are in a user’s filesystem. where their created Paper docs are stored) by calling /users/features/get_values. Once migrations begin, you can check the state of a user (i.e. paper files and will eventually migrate all users by Q2 2022. Over the coming months, we’ll offer a way for existing users to migrate their docs to. There won’t be any change to new docs created by existing Paper users. paper files alongside their other Dropbox content.
New Paper users will see Paper docs they create as. The following timeline and guide will help you migrate from using /paper/ endpoints to their equivalent /files/ endpoints to work with a user’s Paper docs in the Dropbox file system: Dates
Duplicate paper dropbox full#
Read on for a full list of API endpoints that you should start using to fetch this new. Instead, the associated /files/ or /sharing/ equivalent API endpoint should be used to interact with a user’s Paper content. This is part of an effort to ensure consistency with where Dropbox and Paper content are stored, and their associated sharing and permissions.Īs part of this change, any existing /paper/ API endpoints that interact directly with Paper content won’t work for new users whose Paper content is stored alongside their Dropbox content. paper files alongside their Dropbox content in the filesystem. Starting in September 25 2019, new Paper users will see Paper docs they create as. Paper API to Paper in the Dropbox API Migration Guide