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
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Folder item collections support paging and selected fields. File downloads return original current file content; metadata, versions and collaborations require their own requests.
Box folder item listing ↗
Folder paging and returned items · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Folder item collections support paging and selected fields. File downloads return original current file content; metadata, versions and collaborations require their own requests.
Box folder item listing ↗
Folder paging and returned items · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
The selected route lists folder contents and retrieves identified files. It does not credit a separate metadata-query product or content-search entitlement.
Box folder item listing ↗
Folder paging and returned items · Checked 2026-10-16
Access cost barrier -
-
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Business plans include licensed monthly API allocations; some customers purchase increased Platform API allocations. Complete minimum-plan and fixed access conditions remain unresolved.
Box API rate limits ↗
User, upload, licensing and retry limits · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
OAuth grants access on behalf of the customer user within scopes and collaborator permissions. Enterprise administrator controls can restrict applications; server-account administration and Marketplace publication are separate routes.
Box OAuth application setup ↗
OAuth setup, scopes and authorized users · Checked 2026-10-16
Downstream permission -
-
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Box OAuth application setup ↗
OAuth setup, scopes and authorized users · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
The upload operation creates a file under an accessible parent folder with file-write permissions. Updating file versions is a separate operation and is not credited here.
Box upload file operation ↗
Upload file and parent-folder access · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Box OAuth application setup ↗
OAuth setup, scopes and authorized users · 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
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
User Events carry file upload, rename, trash and collaboration changes. Events can be duplicated or out of order, so persist event IDs and reconcile current folder contents.
Box user Events feed ↗
Event types, stream position and retention limitations · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
General calls are limited to 1,000 requests/minute/user; uploads allow 240/minute/user and search has separate governors. Monthly licensed allocations also apply; 429 includes retry-after.
Box API rate limits ↗
User, upload, licensing and retry limits · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
User Events include ITEM_UPLOAD, ITEM_RENAME and ITEM_TRASH with event identities for the authorized user’s file scope.
Box user Events feed ↗
Event types, stream position and retention limitations · Checked 2026-10-16
Replay and gap recovery 7.5/10
Replay/change queries within a documented retention window
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
User Events are retained between two weeks and two months; stream_position supports catch-up, with duplicates/out-of-order events and no indefinite history.
Box user Events feed ↗
Event types, stream position and retention limitations · 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
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Original downloadable file bytes can leave Box and be used independently. Folder ZIP/browser copies have limits; Box Notes, complete versions, collaborations and workflow behavior remain outside this file-payload score.
Box original file download ↗
Download current file content · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Box original file download ↗
Download current file content · Checked 2026-10-16
Planned migration fidelity 10.0/10
Original objects or native schema/data with a documented independent restore/use path
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Original downloadable file bytes can leave Box and be used independently. Folder ZIP/browser copies have limits; Box Notes, complete versions, collaborations and workflow behavior remain outside this file-payload score.
Box original file download ↗
Download current file content · 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
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
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).
Box OAuth application setup ↗
OAuth setup, scopes and authorized users · Checked 2026-10-16
Rights to custom logic -
-
Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Box OAuth application setup ↗
OAuth setup, scopes and authorized users · 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
OAuth grants access on behalf of the customer user within scopes and collaborator permissions. Enterprise administrator controls can restrict applications; server-account administration and Marketplace publication are separate routes.
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
Folder item collections support paging and selected fields. File downloads return original current file content; metadata, versions and collaborations require their own requests. The selected route lists folder contents and retrieves identified files. It does not credit a separate metadata-query product or content-search entitlement.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 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
Business plans include licensed monthly API allocations; some customers purchase increased Platform API allocations. Complete minimum-plan and fixed access conditions remain unresolved.
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
The upload operation creates a file under an accessible parent folder with file-write permissions. Updating file versions is a separate operation and is not credited here.
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
User Events carry file upload, rename, trash and collaboration changes. Events can be duplicated or out of order, so persist event IDs and reconcile current folder contents. General calls are limited to 1,000 requests/minute/user; uploads allow 240/minute/user and search has separate governors. Monthly licensed allocations also apply; 429 includes retry-after.
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 resourcesBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. User Events include ITEM_UPLOAD, ITEM_RENAME and ITEM_TRASH with event identities for the authorized user’s file scope. | Box user Events feed ↗Event types, stream position and retention limitationsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Replay/change queries within a documented retention windowBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. User Events are retained between two weeks and two months; stream_position supports catch-up, with duplicates/out-of-order events and no indefinite history. | Box user Events feed ↗Event types, stream position and retention limitationsChecked 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
Original downloadable file bytes can leave Box and be used independently. Folder ZIP/browser copies have limits; Box Notes, complete versions, collaborations and workflow behavior remain outside this file-payload 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 scopeBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Folder item collections support paging and selected fields. File downloads return original current file content; metadata, versions and collaborations require their own requests. | Box folder item listing ↗Folder paging and returned itemsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Folder item collections support paging and selected fields. File downloads return original current file content; metadata, versions and collaborations require their own requests. | Box folder item listing ↗Folder paging and returned itemsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. The selected route lists folder contents and retrieves identified files. It does not credit a separate metadata-query product or content-search entitlement. | Box folder item listing ↗Folder paging and returned itemsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. OAuth grants access on behalf of the customer user within scopes and collaborator permissions. Enterprise administrator controls can restrict applications; server-account administration and Marketplace publication are separate routes. | Box OAuth application setup ↗OAuth setup, scopes and authorized usersChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Business plans include licensed monthly API allocations; some customers purchase increased Platform API allocations. Complete minimum-plan and fixed access conditions remain unresolved. | Box API rate limits ↗User, upload, licensing and retry limitsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Box OAuth application setup ↗OAuth setup, scopes and authorized usersChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. The upload operation creates a file under an accessible parent folder with file-write permissions. Updating file versions is a separate operation and is not credited here. | Box upload file operation ↗Upload file and parent-folder accessChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Customers can build or choose applications using the documented API and the disclosed authorization route. | Box OAuth application setup ↗OAuth setup, scopes and authorized usersChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. User Events carry file upload, rename, trash and collaboration changes. Events can be duplicated or out of order, so persist event IDs and reconcile current folder contents. | Box user Events feed ↗Event types, stream position and retention limitationsChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. General calls are limited to 1,000 requests/minute/user; uploads allow 240/minute/user and search has separate governors. Monthly licensed allocations also apply; 429 includes retry-after. | Box API rate limits ↗User, upload, licensing and retry limitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Original objects or portable records delivered to a customer-selected destinationBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Original downloadable file bytes can leave Box and be used independently. Folder ZIP/browser copies have limits; Box Notes, complete versions, collaborations and workflow behavior remain outside this file-payload score. | Box original file download ↗Download current file contentChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Box original file download ↗Download current file contentChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. 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). | Box OAuth application setup ↗OAuth setup, scopes and authorized usersChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Box / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Box OAuth application setup ↗OAuth setup, scopes and authorized usersChecked 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 pathBox / customer-authorized OAuth, original downloadable files, folder listings, uploads and user Events feed; enterprise-wide audit, Box Notes conversion and full permissions/version migration are separate. Original downloadable file bytes can leave Box and be used independently. Folder ZIP/browser copies have limits; Box Notes, complete versions, collaborations and workflow behavior remain outside this file-payload score. | Box original file download ↗Download current file contentChecked 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.