Integrate the Filevine API.Caddi writes and runs the integration for you.
Filevine has a REST API (v2) served through its API Gateway. An account admin at your firm generates a personal access token and client credentials in Filevine's Account Manager, which are exchanged for a short-lived bearer token. Software vendors go through Filevine's Certified Partner program.
- 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. Filevine uses token-bucket rate limits by API tier (a steady rate plus a burst), and customers can ask for increases.
Register an app, store Filevine credentials, refresh tokens and code around the rate limits.
Connect your Filevine account once. Caddi holds the connection.
The job doesn't stop at Filevine.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Filevine API only reaches Filevine.
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. Client secrets expire after a year and have to be rotated.
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 Filevine API gives you
- Type
- REST (JSON), v2
- Authentication
- Personal access token
- Who can get access
- An account admin at your firm generates a personal access token and client credentials in Filevine's Account Manager, which are exchanged for a short-lived bearer token. Software vendors go through Filevine's Certified Partner program.
- What it covers
- Projects, contacts, documents, notes, appointments, collection sections, billing items, invoices and payments, plus webhooks.
- Limits
- Filevine uses token-bucket rate limits by API tier (a steady rate plus a burst), and customers can ask for increases.
- Worth knowing
- Client secrets expire after a year and have to be rotated.
Official docs: developer.filevine.io. Checked September 2026. Vendors change access terms, so confirm with Filevine before you build.
When to build the Filevine 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 Filevine work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Filevine API for
Inbound packet to project
Caddi reads inbound intake packets, opens the Filevine project, files the docs, and creates the standard set of activities and deadlines.
Medical records chase
Caddi generates HIPAA authorization requests from Filevine project data, sends them, and tracks responses against each project.
Settlement archive
When a project closes, Caddi assembles the final settlement archive, files it to the DMS, and updates Filevine with the closeout state.
Everything Caddi does with Filevine.
Filevine API questions
Does Filevine have an API?
Yes. Filevine has a REST API (v2) served through its API Gateway, authenticated with Personal access token. The official documentation is at https://developer.filevine.io/docs/v2-us.
How do I get access to the Filevine API?
An account admin at your firm generates a personal access token and client credentials in Filevine's Account Manager, which are exchanged for a short-lived bearer token. Software vendors go through Filevine's Certified Partner program.
Does the Filevine API have rate limits?
Filevine uses token-bucket rate limits by API tier (a steady rate plus a burst), and customers can ask for increases.
Can I connect Filevine to my other tools without writing code against its API?
Yes. With Caddi you show the Filevine task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Filevine 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 Filevine with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Filevine is reviewed before it runs in production, and every run is logged.