ShareFile APIConnect ShareFile without building on its API
ShareFile has a REST API. Self-serve for customers only (API keys come from a ShareFile account's settings). If you're reading the docs because you need ShareFile 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 ShareFile and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve for customers
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.
Building on the ShareFile API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get ShareFile credentials, and manage tokens and refreshes. | Connect your ShareFile 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 ShareFile 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 ShareFile work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect ShareFile without the build.
Drop your work email and pick a time. We'll show you Caddi running your ShareFile workflow end to end.