canonical: https://jentic.com/apis/filevine.io/filevine # Filevine API 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. Authentication is performed by sending the x-fv-secretkey header containing a Filevine secret key. The API is used by law firms and legal operations teams that need to automate case intake, document filing, and task assignment without manual entry into the Filevine web UI. ## For AI 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. ## Scope Does not handle billing and time entry, e-signature collection, or court e-filing - use for case, contact, task, note, and document management on Filevine projects only. ## Capabilities - 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 - Upload and list case documents, then organise them in the project's document tree - Read and write custom field values that drive Filevine's case-specific data model ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance, so the agent never handles the credential. Integration drops from a multi-day Filevine API project to under an hour. Example prompt: 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 | 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 | ## Key resources - **Projects** — Filevine cases - the top-level container for legal matters - **Contacts** — Clients, witnesses, opposing counsel, and other parties on a case - **Tasks** — Assigned work items with due dates against a project - **Notes** — Free-text notes attached to a project for activity history - **Documents** — Files attached to a Filevine project - **Custom Fields** — Project-type-specific structured data driving Filevine's data model ## Why Jentic - **Setup:** Wiring the Filevine API by hand means sending the x-fv-secretkey header, pointing at the v2 base, and threading project and contact ids through the case-management routes yourself. Through Jentic you install once, import the Filevine API from the API Directory, store the secret key once, and your agent calls it. - **Permission scoping:** Filevine puts the project id and contact id in the URL path (`/projects/{id}`, `/contacts/{id}`), so a rule can pin your agent to the projects you allow. You choose the operations it may call, so a destructive action like deleting a project is not included unless you add it to the read and update operations. - **Credential handling:** Your Filevine secret key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw x-fv-secretkey value never enters the agent's prompt, logs, or context, even on retries. - **Discovery method:** Agents search Jentic by intent such as 'create a new legal case' or 'add a contact', and Jentic returns the matching Filevine operation with its input schema, so the agent calls the right endpoint without reading the spec. ## Related APIs - **Salesforce REST API** — Generic case object can be customised but lacks legal-specific defaults - **HubSpot CRM Deals API** — General CRM with deal pipelines used by some smaller firms in lieu of legaltech - **Dropbox API** — Source documents to upload into Filevine cases ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the Filevine API? Yes. Because you run Jentic One yourself, your own rules decide which Filevine operations the agent may call and which credentials it may use. Filevine puts the project id and contact id in the URL path (`/projects/{id}`, `/contacts/{id}`), so you can pin the agent to the specific projects you allow. You choose the operations it is granted, so a destructive call like DELETE `/projects/{id}` stays out of reach unless you add it alongside the read and update endpoints.