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