Box APIConnect Box without building on its API
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. If you're reading the docs because you need Box to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Box and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
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.
Building on the Box API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Box credentials, and manage tokens and refreshes. | Connect your Box account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Box task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Box work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect Box without the build.
Drop your work email and pick a time. We'll show you Caddi running your Box workflow end to end.