Plan your integration

Assess your use case

Content-centric processes perform best on Box. Ask yourself:

Is content always involved in the process?
Does the process involve:
- moving content from one place to another,
- collecting e-signatures,
- generating documents,
- automating multi-step review, approval, or routing workflows,
- answering questions about content or extracting metadata with AI,
- building purpose-built agents or custom AI extractions,
- publishing governed knowledge portals for teams or departments,
- classifying, protecting, or monitoring sensitive content for threats,
- or applying retention schedules, legal holds, or other compliance controls?
Can the workflow abide by ?
Does the process involve administrative tasks that may be automated?

If you answered yes to these questions, you most likely have a strong use case for Box. Many teams also build on Box for AI-first workflows: agents that work across authorized content, curated knowledge shared at org scale, and documents generated from templates. Common solutions include:

Use case	Example Box products
Agentic file system	and the so agents search, reason over, and act on files a user can access; for building integrations with coding assistants; and to trigger downstream automation.
Company Brain	as governed knowledge portals, for permissions-aware answers across hub content, for purpose-built agents, and for structured context.
Team and department knowledge portals (Hubs)	to create and populate portals programmatically, for natural-language search within a hub, and to surface hubs in internal apps — see the .
Template-based document generation	to merge structured data into Word templates and output PDFs; often paired with for approval and signature — see the .
Marketing asset management	for curated libraries, and for discovery, and for browse and preview experiences.
Secure document vaults	for classification and threat detection, for retention and , plus on files and folders.
Content classification	to label files and folders by sensitivity, to suggest or auto-apply labels at scale, and to enforce classification-based access policies and detect threats.
Wealth management portals	Custom Platform Apps with or , for client agreements, and metadata for client or account context.
Automatic folder creation based on user provisioning	, , and APIs, plus to react to user lifecycle events
Adding relevant metadata using AI	to extract or suggest metadata, for custom agents.
Claim reviews with built-in approval and rejection flows	for review workflows, for approvals and signatures, and to generate claim or decision letters.
Event monitoring for security and auditing	and for real-time activity, alerts, and Box Governance reporting for retention and hold activity.

Product availability depends on your Box plan and enterprise entitlements. Not every product is included on the free developer plan. See for paid tiers and add-on products.

Still not sure if you have a good use case? Reach out to your Box account team or our sales team at sales@box.com.

Choose an application type

Box applications support different capabilities and authentication options.

Platform App

cover most use cases. They let you present Box functionality in a custom interface, including for browsing, searching, and previewing content. When you create a Platform App, you select an app type:

User — for user-facing apps (OAuth 2.0)
Server — for backend services using Client Credentials Grant or JWT

Platform Apps are a good fit when you need to access your own files and others’ files, upload and download content, and optionally list the app in Box Integrations.

Web App Integrations

let third-party applications work inside the Box user experience. Users can edit, share, or modify Box content with your app, and you can surface the integration in Recommended Web Integrations in Box Preview.

Publish your app

is where Box users discover apps that work with Box. Listing your app is an effective way to reach new users, especially for apps meant for other enterprises. To publish, make sure your app is production-ready and uses OAuth 2.0. Submit it for approval in the Developer Console:

Select Apps.
Select Submit for Approval.
Fill out the form and select Submit.

Approved apps can appear in featured, most popular, or recently added sections. For the submission checklist, required assets, and partner review process, see .

Non-OAuth integrations cannot use that listing flow as-is; the guide describes using an OAuth listing as a marketing redirect when needed.

Questions about publishing: integrate@box.com.

Next steps

— review the full listing checklist, required assets, and partner review process
to build a working integration end to end

Getting started

Applications & integrations

Identity & access

Using the API

Troubleshooting

Content

Collaboration

Metadata & search

Events & webhooks

Users

Intelligent workflow

E-signatures

Security & compliance

Assess your use case

Choose an application type

Platform App

Web App Integrations

Publish your app

Next steps

​Assess your use case

​Choose an application type

​Platform App

​Web App Integrations

​Publish your app

​Next steps

Assess your use case

Choose an application type

Platform App

Web App Integrations

Publish your app

Next steps