Harvey is a legal AI platform for agents, Assistant, Vault documents, client matters, Intake, audit logs, and usage history.
Add one processed file or a group of processed files to a Harvey review table and schedule asynchronous review processing. A successful response confirms scheduling, not completion. This contract is documentation-derived and has not been live-verified.
Start an asynchronous Harvey agent run from a prompt and optional documents. The documented contract and permissions have not been live-verified; use Get Agent Thread with the returned id to retrieve the final result.
Generate one non-streaming Harvey Assistant response from a prompt with optional documents or knowledge sources, matter attribution, model selection, and citations. This API requires an additional paid workspace purchase. Its documented contract and permissions have not been live-verified.
Create time-limited pre-signed download URLs for file IDs returned by Harvey query-history exports. The URLs grant temporary file access and must be treated as secrets: use them promptly and do not log, publish, or share them. This operation's API-token permission is not specified by Harvey, and the contract has not been live-verified.
Submit an idempotent request and optional documents to the Harvey Intake queue. A new request returns HTTP 201 and a replay of the caller-provided idempotency key returns the original request with HTTP 200. This documented contract and its permissions have not been live-verified.
Create a Harvey Vault project or knowledge base, optionally attributed to a client matter. This documented contract and its permissions have not been live-verified.
Idempotently soft-delete 1 to 10,000 Harvey matters by firm client and matter identifiers. Inspect deleted, already_absent, and errors even on HTTP 200 because a batch can partially succeed. The parent clients and historical queries remain. This contract is documentation-derived and has not been live-verified.
Permanently delete one file from a Harvey Vault project. WARNING: this is a destructive operation and the file cannot be recovered through this action. Harvey may complete deletion asynchronously, so a successful response can confirm acceptance rather than immediate removal. The response preserves any operation or status identifier for follow-up. This contract is documentation-derived and has not been live-verified.
Move an entire Harvey Vault project and all its contents to the workspace recycle bin. This is destructive and processing continues asynchronously after Harvey accepts the request, so the response does not prove completion. Confirm the project ID and intended contents before calling. This contract and its permissions are documentation-derived and have not been live-verified.
Export enriched query history for a UTC epoch window of at most 30 days, optionally including related file IDs. Warning: results contain sensitive workspace-wide resource names, prompts, and AI outputs and are not restricted by client-matter or ethical-wall boundaries. Share results and API tokens carefully. Harvey limits History Export endpoints to two requests per minute. This documented contract has not been live-verified.
Export enriched Harvey workspace usage events for a UTC epoch range of at most 30 days, optionally including related file IDs. The data may contain sensitive resource names across the entire workspace and is not bounded by client-matter or ethical-wall access. Harvey limits History Export endpoints to 2 requests per minute. This contract is documentation-derived and has not been live-verified.
Return metadata for one reachable published Harvey agent. Use this before starting a run to confirm the agent remains available and identify its current published version. This contract is documentation-derived and not live-verified.
Read one Harvey agent thread status and any available answer, citations, generated files, or error. This contract is documentation-derived and has not been live-verified.
Return the Harvey service-user identity associated with the connected API token. Harvey documents this as its authentication-test endpoint but does not document whether it needs a configurable token permission. No no-permission claim is made, and this has not been live-verified.
Return the earliest available Harvey audit log, optionally filtered by log type. Use its ID to begin forward audit-log traversal. This contract is documentation-derived and has not been live-verified.
Read one Harvey Intake request's lifecycle state, assignment, timestamps, and attachments. This contract is documentation-derived and has not been live-verified.
Return the latest available Harvey audit log, optionally for one log type. This contract is documentation-derived and has not been live-verified.
Return a Harvey review table's title, creation time, and associated file IDs. This contract is documentation-derived and has not been live-verified.
Return a Harvey review-table row and its cell results for one file. Files in a group resolve to the shared row. This contract is documentation-derived and has not been live-verified.
Return details and processing status for up to 1,000 Harvey Vault file IDs. Files that are missing or inaccessible are returned as records with an error instead of file details. This contract is documentation-derived and has not been live-verified.
Return a Harvey Vault project's metadata, file identifiers and names, review tables, and storage limits. This contract, including the provider's unusual HTTP 201 success response for a GET request, is documentation-derived and has not been live-verified.
List published Harvey agents available to the connected service user, one cursor page at a time. This contract is documentation-derived and has not been live-verified.
Page forward through Harvey audit logs from a starting log ID, optionally filtered by log type. Continuation advances from the last returned log ID. This pagination contract is documentation-derived and has not been live-verified; the inclusive or exclusive boundary behavior must be confirmed to rule out duplicate rows.
Return all Harvey client matters, including deleted records and usage statistics. This unpaginated contract is documentation-derived and has not been live-verified.
List Vault projects currently in the workspace recycle bin, optionally filtered by project-name text or client matter. Results retain Harvey's newest-deletion-first order. This contract is documentation-derived and has not been live-verified.
List, filter, and sort files in a Harvey Vault project, one cursor page at a time. The response and pagination contract is documentation-derived and has not been live-verified.
List workspace users with direct or inherited effective access to a Harvey Vault project. The project owner is included with MANAGE access, and provider-returned access-origin, inherited-access, and owner indicators are preserved when present. Requires Vault API plus either Vault sharing (view only) or Vault sharing permission. This response contract and permission behavior are documentation-derived and have not been live-verified.
List and filter workspace Vault projects and knowledge bases, one page at a time. The response and pagination contract is documentation-derived and has not been live-verified.
Remove direct WORKSPACE_USER shares from a Harvey Vault project by email. Inherited access through workspace, group, or space shares remains effective. Inspect both removed and failed because individual emails can fail without rejecting the entire request. This contract is documentation-derived and has not been live-verified.
Return the first Harvey audit log at or after a UTC epoch timestamp, optionally filtered by log type. This contract is documentation-derived and has not been live-verified.
Return semantically relevant document chunks from one Harvey Vault project. The response is ordered by relevance and can optionally include source file names. This contract has not been live-verified.
Add workspace users or update their direct access level on a Harvey Vault project. This is an additive partial update: users omitted from the request remain unchanged, and the project owner must not be included. Inspect failed even on HTTP 200 because individual user updates can fail. This contract and its permissions are documentation-derived and have not been live-verified.
Upload up to 50 new or replacement files to a Harvey Vault project. Optional Vault paths correspond positionally to the uploaded files, and duplicate_mode controls filename collisions. The provider returns HTTP 201. This documented contract and its permissions have not been live-verified.
Create, update, or restore up to 10,000 Harvey clients by firm client identifier. Always inspect the returned errors array because Harvey can report row-level failures alongside successful rows in HTTP 200 responses. This contract is documentation-derived and has not been live-verified.
Create, update, or restore up to 10,000 Harvey matters under existing clients. Inspect errors even on HTTP 200 because valid rows can succeed while other rows fail. The connected API token needs Harvey's Client matters admin (write:client_matters) permission; sending allowed on any row additionally needs use:disallowed_client_matters. These are Harvey API-token permissions, not OAuth scopes. This contract and its permissions are documentation-derived and have not been live-verified.
The Harvey integration connects your Dench AI CRM directly to Harvey, so agents can read and act on your Harvey data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
35 actions are available for agents to invoke on your behalf. Every call runs through Harvey's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Harvey and click Connect — you'll authorize access through Harvey's own sign-in flow. No API keys or code required.
Ask an agent to use Harvey in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Harvey integration connects your AI CRM to Harvey, so AI agents can work with your Harvey data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Harvey integration currently exposes 35 actions, including Add Review Table Row, Create Agent Thread, Create Assistant Completion, Create History File Download URLs, Create Intake Request, and Create Vault Project. Agents invoke them on your behalf from chat or from automations.
No. You connect Harvey from your Dench workspace using Harvey's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Harvey's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Harvey connection from your workspace settings at any time.