OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
list_folder and continue enumerate selected paths and metadata, with file IDs that survive moves and renames. has_more must be exhausted before saving the latest cursor.
Dropbox file access and traversal ↗
File IDs, folder paging, deleted and non-downloadable content · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
list_folder and continue enumerate selected paths and metadata, with file IDs that survive moves and renames. has_more must be exhausted before saving the latest cursor.
Dropbox file access and traversal ↗
File IDs, folder paging, deleted and non-downloadable content · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Folder paths, recursive traversal and metadata lookup provide scoped retrieval; the assessed route is not SQL over file contents.
Dropbox file access and traversal ↗
File IDs, folder paging, deleted and non-downloadable content · Checked 2026-10-16
Access cost barrier -
-
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Storage-plan entitlement and monthly upload limits differ from API throughput. The reviewed sources do not establish all fixed access charges relative to the lowest paid plan.
Dropbox API error and limit handling ↗
429 responses and namespace contention · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 7.5/10
Open registration under published review criteria
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Users authorize OAuth scopes and App Folder or broader access. Broad public distribution has a production-status review boundary; team access and member impersonation need separate scopes and administrator grants.
Dropbox application production review ↗
Development status and production approval · Checked 2026-10-16
Downstream permission -
-
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Dropbox OAuth authorization ↗
Scopes, user/team tokens and refresh tokens · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
files/upload creates or replaces file content using declared write mode. Larger uploads require upload sessions, and simultaneous namespace writes can be rate limited.
Dropbox upload operation ↗
Upload parameters and write mode · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Third-party production applications use the documented provider approval route before the customer authorizes the fixed API interface.
Dropbox application production review ↗
Development status and production approval · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Folder cursors return file additions/updates and deletion entries. Cursors can expire after extended nonuse; 409 reset requires new folder enumeration, while path errors can indicate the folder itself was deleted.
Dropbox file change detection ↗
Folder cursors, reset and path errors · Checked 2026-10-16
Limit visibility 7.5/10
Service-specific limits disclosed in runtime headers
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Dropbox returns 429 for request volume or concurrent namespace writes and may supply Retry-After. A universal numeric request ceiling is not published in the reviewed guide.
Dropbox API error and limit handling ↗
429 responses and namespace contention · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Folder continue returns add/modify and deletion entries. Preserve stable file IDs and namespace context instead of relying only on mutable paths.
Dropbox file change detection ↗
Folder cursors, reset and path errors · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
The saved cursor resumes changes while valid. On 409 reset, enumerate again; no guaranteed elapsed-time replay window is established.
Dropbox file change detection ↗
Folder cursors, reset and path errors · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 10.0/10
Original objects or portable records delivered to a customer-selected destination
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Downloadable original files can be held and used outside Dropbox. Browser folder download supplies a local copy; cloud-native conversion, sharing permissions and full version history are outside this original-file score.
Dropbox original file download ↗
File downloads and non-downloadable exclusions · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Dropbox original file download ↗
File downloads and non-downloadable exclusions · Checked 2026-10-16
Planned migration fidelity 10.0/10
Original objects or native schema/data with a documented independent restore/use path
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Downloadable original files can be held and used outside Dropbox. Browser folder download supplies a local copy; cloud-native conversion, sharing permissions and full version history are outside this original-file score.
Dropbox original file download ↗
File downloads and non-downloadable exclusions · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Dropbox OAuth authorization ↗
Scopes, user/team tokens and refresh tokens · Checked 2026-10-16
Rights to custom logic -
-
Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Dropbox OAuth authorization ↗
Scopes, user/team tokens and refresh tokens · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Users authorize OAuth scopes and App Folder or broader access. Broad public distribution has a production-status review boundary; team access and member impersonation need separate scopes and administrator grants.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
list_folder and continue enumerate selected paths and metadata, with file IDs that survive moves and renames. has_more must be exhausted before saving the latest cursor. Folder paths, recursive traversal and metadata lookup provide scoped retrieval; the assessed route is not SQL over file contents.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | Yes | App review | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Storage-plan entitlement and monthly upload limits differ from API throughput. The reviewed sources do not establish all fixed access charges relative to the lowest paid plan.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
files/upload creates or replaces file content using declared write mode. Larger uploads require upload sessions, and simultaneous namespace writes can be rate limited.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Folder cursors return file additions/updates and deletion entries. Cursors can expire after extended nonuse; 409 reset requires new folder enumeration, while path errors can indicate the folder itself was deleted. Dropbox returns 429 for request volume or concurrent namespace writes and may supply Retry-After. A universal numeric request ceiling is not published in the reviewed guide.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Folder continue returns add/modify and deletion entries. Preserve stable file IDs and namespace context instead of relying only on mutable paths. | Dropbox file change detection ↗Folder cursors, reset and path errorsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. The saved cursor resumes changes while valid. On 409 reset, enumerate again; no guaranteed elapsed-time replay window is established. | Dropbox file change detection ↗Folder cursors, reset and path errorsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Downloadable original files can be held and used outside Dropbox. Browser folder download supplies a local copy; cloud-native conversion, sharing permissions and full version history are outside this original-file score.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. list_folder and continue enumerate selected paths and metadata, with file IDs that survive moves and renames. has_more must be exhausted before saving the latest cursor. | Dropbox file access and traversal ↗File IDs, folder paging, deleted and non-downloadable contentChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. list_folder and continue enumerate selected paths and metadata, with file IDs that survive moves and renames. has_more must be exhausted before saving the latest cursor. | Dropbox file access and traversal ↗File IDs, folder paging, deleted and non-downloadable contentChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Folder paths, recursive traversal and metadata lookup provide scoped retrieval; the assessed route is not SQL over file contents. | Dropbox file access and traversal ↗File IDs, folder paging, deleted and non-downloadable contentChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Open registration under published review criteriaDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Users authorize OAuth scopes and App Folder or broader access. Broad public distribution has a production-status review boundary; team access and member impersonation need separate scopes and administrator grants. | Dropbox application production review ↗Development status and production approvalChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Storage-plan entitlement and monthly upload limits differ from API throughput. The reviewed sources do not establish all fixed access charges relative to the lowest paid plan. | Dropbox API error and limit handling ↗429 responses and namespace contentionChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Dropbox OAuth authorization ↗Scopes, user/team tokens and refresh tokensChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. files/upload creates or replaces file content using declared write mode. Larger uploads require upload sessions, and simultaneous namespace writes can be rate limited. | Dropbox upload operation ↗Upload parameters and write modeChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Third-party production applications use the documented provider approval route before the customer authorizes the fixed API interface. | Dropbox application production review ↗Development status and production approvalChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Folder cursors return file additions/updates and deletion entries. Cursors can expire after extended nonuse; 409 reset requires new folder enumeration, while path errors can indicate the folder itself was deleted. | Dropbox file change detection ↗Folder cursors, reset and path errorsChecked 2026-10-16 |
| How are integration limits disclosed? | Service-specific limits disclosed in runtime headersDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Dropbox returns 429 for request volume or concurrent namespace writes and may supply Retry-After. A universal numeric request ceiling is not published in the reviewed guide. | Dropbox API error and limit handling ↗429 responses and namespace contentionChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Original objects or portable records delivered to a customer-selected destinationDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Downloadable original files can be held and used outside Dropbox. Browser folder download supplies a local copy; cloud-native conversion, sharing permissions and full version history are outside this original-file score. | Dropbox original file download ↗File downloads and non-downloadable exclusionsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Dropbox original file download ↗File downloads and non-downloadable exclusionsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Dropbox OAuth authorization ↗Scopes, user/team tokens and refresh tokensChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Dropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Dropbox OAuth authorization ↗Scopes, user/team tokens and refresh tokensChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Original objects or native schema/data with a documented independent restore/use pathDropbox / OAuth user file access, downloadable original file payloads and folder cursors; cloud-native documents requiring conversion, full team administration and historic versions beyond retention are excluded. Downloadable original files can be held and used outside Dropbox. Browser folder download supplies a local copy; cloud-native conversion, sharing permissions and full version history are outside this original-file score. | Dropbox original file download ↗File downloads and non-downloadable exclusionsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.