Integrate the ShareFile API.Caddi writes and runs the integration for you.
ShareFile has a REST API. Self-serve for customers only (API keys come from a ShareFile account's settings).
- 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.
Register an app, store ShareFile credentials, refresh tokens.
Connect your ShareFile account once. Caddi holds the connection.
The job doesn't stop at ShareFile.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The ShareFile API only reaches ShareFile.
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 ShareFile API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0
- Who can get access
- Self-serve for customers only (API keys come from a ShareFile account's settings).
- What it covers
- Users, items (files/folders), groups, shares, workflows, webhooks, storage zones, policies and reports.
Official docs: api.sharefile.com. Checked September 2026. Vendors change access terms, so confirm with ShareFile before you build.
When to build the ShareFile 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 ShareFile work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the ShareFile API for
Client request + collection
Caddi generates the personalized ShareFile request, sends it to the client, and tracks completion.
Inbound classification + filing
When documents land in ShareFile, Caddi classifies them, applies the firm's metadata, and files them in the DMS or matter system.
Completion notify + record update
When a ShareFile request completes, Caddi updates the source record and notifies the owner that the docs are in.
Everything Caddi does with ShareFile.
ShareFile API questions
Does ShareFile have an API?
Yes. ShareFile has a REST API, authenticated with OAuth 2.0. The official documentation is at https://api.sharefile.com/.
How do I get access to the ShareFile API?
Self-serve for customers only (API keys come from a ShareFile account's settings).
Can I connect ShareFile to my other tools without writing code against its API?
Yes. With Caddi you show the ShareFile task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across ShareFile 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 ShareFile with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for ShareFile is reviewed before it runs in production, and every run is logged.