Integrate the Box API.Caddi writes and runs the integration for you.
Box has a REST API. Self-serve for any developer (a free developer account gives access to the Developer Console); server apps (JWT/CCG) need enterprise admin authorization.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. 1,000 requests/min per user in general, 240 uploads/min per user, and search capped at 60/min per user.
Register an app, store Box credentials, refresh tokens and code around the rate limits.
Connect your Box account once. Caddi holds the connection.
The job doesn't stop at Box.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Box API only reaches Box.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the Box API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0, JWT, Client Credentials Grant, or a Developer Token for testing
- Who can get access
- Self-serve for any developer (a free developer account gives access to the Developer Console); server apps (JWT/CCG) need enterprise admin authorization.
- What it covers
- Files, folders, users, groups, collaborations, metadata, search, webhooks, and Box Sign.
- Limits
- 1,000 requests/min per user in general, 240 uploads/min per user, and search capped at 60/min per user.
Official docs: developer.box.com. Checked September 2026. Vendors change access terms, so confirm with Box before you build.
When to build the Box integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Box work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Box API for
Intake PDF Filing
Caddi extracts client and contract details from intake PDFs, renames and files them to the right submissions folder, and updates the submission tracker.
Account Record Creation
Caddi extracts required details from account-opening PDFs and creates the linked household, person, and new account form records, reducing manual data entry for client services teams.
Signed-doc post-processing
When a signed document lands in Box, Caddi applies the firm's metadata, updates the related CRM record, and notifies the owner.
Folder hygiene loop
Caddi normalizes filenames, dedupes copies, and reroutes misfiled documents on a nightly schedule based on your firm's rules.
Everything Caddi does with Box.
Box API questions
Does Box have an API?
Yes. Box has a REST API, authenticated with OAuth 2.0, JWT, Client Credentials Grant, or a Developer Token for testing. The official documentation is at https://developer.box.com/.
How do I get access to the Box API?
Self-serve for any developer (a free developer account gives access to the Developer Console); server apps (JWT/CCG) need enterprise admin authorization.
Does the Box API have rate limits?
1,000 requests/min per user in general, 240 uploads/min per user, and search capped at 60/min per user.
Can I connect Box to my other tools without writing code against its API?
Yes. With Caddi you show the Box task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Box and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate Box with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Box is reviewed before it runs in production, and every run is logged.