Filevine API

Name: Filevine API API
Brand: Filevine API
Availability: InStock

✓ Official Vendor SpecProductivityTask ManagementapiKey35 EndpointsREST

For Agents

Manage Filevine cases, contacts, tasks, notes, documents, and custom fields via the x-fv-secretkey header. Useful for agents automating legal case intake and task tracking.

Connect the Filevine API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Filevine API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Filevine API API.

Open a new Filevine project (case) and assign initial team members

Create and update contacts so a case is linked to client, opposing counsel, and witnesses

Assign tasks to staff with due dates and surface upcoming deadlines per case

Append notes to a project to capture call summaries and intake interviews

GET STARTED

Start building with Filevine API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Filevine API API for, with concrete tasks.

★ Intake-Form-To-Case Automation

Personal injury and mass tort firms can have an agent receive a web intake submission, call POST /projects to open the case, then POST /contacts and link the contact to the project. The agent finishes by creating the standard intake task list via POST /tasks. A workflow that previously took an intake clerk twenty minutes per matter completes in seconds.

Call POST /projects with the case template, POST /contacts for the lead, then POST /tasks for each step in the intake checklist.

Case Document Filing

Operations teams can route incoming PDFs (scanned mail, signed retainers, medical records) to an agent that classifies the document and calls POST /projects/{id}/documents on the right Filevine case. The agent then drops a note onto the case with the source and routing rationale, keeping a clean audit trail.

Classify the PDF, look up the matching project, call POST documents on that project, then call POST notes summarising the filing.

Deadline Compliance Reporting

Litigation managers can have an agent walk every active project, call GET /projects/{id}/tasks, and produce a daily report of tasks due in the next 7 days that are still open. Filevine returns task due dates, so the agent can prioritise by deadline severity and surface at-risk matters before deadlines slip.

Iterate GET /projects, then GET /projects/{id}/tasks for each, filter open tasks with due_date in the next 7 days, and emit a digest grouped by assignee.

AI Agent Filevine Integration via Jentic

An agent connected to Jentic can search by intent (for example create a new case from an intake) and Jentic returns the right Filevine operation along with its input schema. The x-fv-secretkey is held in the Jentic vault, so the agent never handles the credential. Integration drops from a multi-day Filevine API project to under an hour.

Search Jentic for create a filevine case, load POST /projects, and execute with the intake payload while Jentic injects the secret key from the vault.

Key Endpoints

35 endpoints — the filevine api is the programmatic surface of the filevine legal case management platform, exposing 35 endpoints across projects (cases), contacts, tasks, notes, documents, and the platform's custom field model.

METHOD

PATH

DESCRIPTION

GET

/projects

List Filevine projects (cases)

POST

/projects

Create a new project

GET

/projects/{id}

Retrieve a specific project

PUT

/projects/{id}

Update a project including custom fields

DELETE

/projects/{id}

Delete a project

GET

/contacts

List contacts

POST

/contacts

Create a contact

GET

/contacts/{id}

Retrieve a contact

GET

/projects

List Filevine projects (cases)

POST

/projects

Create a new project

GET

/projects/{id}

Retrieve a specific project

PUT

/projects/{id}

Update a project including custom fields

DELETE

/projects/{id}

Delete a project

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Filevine secret keys (x-fv-secretkey) are stored encrypted in the Jentic vault. Agents receive scoped references; the raw key never enters the agent's context, even on retries.

Intent-based discovery

Agents search Jentic by intent (for example create a new legal case) and Jentic returns the matching Filevine operation with its input schema, so the agent calls the right endpoint without reading the spec.

Time to first call

Direct Filevine integration: 3-5 days for auth, custom field mapping, and document upload handling. Through Jentic: under one hour - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Salesforce REST API

Generic case object can be customised but lacks legal-specific defaults

Choose Salesforce when the firm already runs on Salesforce and the legal data model has been built out as custom objects.

Alternative

HubSpot CRM Deals API

General CRM with deal pipelines used by some smaller firms in lieu of legaltech

Choose HubSpot when the firm is small and the workflow is closer to a sales pipeline than legal case management.

Complementary

Dropbox API

Source documents to upload into Filevine cases

Use Dropbox alongside Filevine when source documents live in firm Dropbox folders and need to be filed onto matters.

FAQs

Specific to using Filevine API API through Jentic.

What authentication does the Filevine API use?

Filevine authenticates with a secret API key sent in the x-fv-secretkey header. Through Jentic the secret key lives in the encrypted vault and is injected at execution; the agent only ever sees a vault reference.

Can I create a new case with the Filevine API?

Yes. Call POST /projects with the project type and required fields. The response returns the project id you then use to attach contacts, tasks, notes, and documents.

What are the rate limits for the Filevine API?

Filevine applies per-org throttling and the spec does not publish a fixed limit. Agents should respect 429 responses with exponential backoff and avoid bursting on /projects listings during business hours.

How do I file a document on a Filevine case via Jentic?

Search Jentic for upload a document to a filevine project, load the documents POST operation, and execute with the project id and document binary. Jentic injects x-fv-secretkey from the vault so the agent never handles the credential.

Can I update custom fields on a Filevine project?

Yes. Use PUT /projects/{id} with the updated custom field values. Filevine's custom field model is project-type specific, so the agent should first read the project to understand which fields are valid for that type.

Is the Filevine API free to use?

API access is included with Filevine subscriptions but typically requires the integrations add-on for production-scale traffic. There is no public free tier.