Skip to main content
The Workspace API lets your systems do the work your team does in Vaquill: create clients and matters, upload documents, run contract review against a playbook, generate and revise drafts, compare versions, build matrices, and pull the results back out as files. It is a different product from the Legal Data API, and the two share nothing.
The two credentials are not interchangeable. A vq_key_ sent to a Workspace route is refused with a wrong-product-credential error that names the other product, and vice versa.

What you can do

Every capability has a page. This is all of them, in the order they appear in the sidebar.

Clients and matters

Create and manage the client, matter and folder structure everything else hangs off.

Documents

Upload at any size, poll ingestion, read extracted text, download the original bytes, delete.

Drafting

Generate a draft, revise it, apply a template, export it.

The draft lifecycle

Import a document as a draft, copy it, file it into a matter, and undo a delete.

Authoring templates

Create, import, edit, copy and retire the boilerplate your drafting runs on.

Contract review

Run a playbook against a contract and get clauses, redlines, missing clauses and negotiation priorities.

Playbook extraction

Read your negotiating positions out of a contract you already signed.

NDA triage

Screen an inbound NDA against ten criteria and your own playbook, for a green, yellow or red answer.

Compliance checks

Check a DPA, a privacy policy or a security plan against one regulation’s requirement checklist.

Compare

Diff two versions of a document and export a redline.

Matrices

Ask the same questions across hundreds of documents and get cited answers.

Matter analysis

A fact ledger, a narrative summary and a timeline, across every document in a matter.

Research and chat

Ask legal questions from your own backend and get grounded, cited answers.

Workflows

Run multi-step pipelines over a set of documents and collect their artifacts.
Two more pages are about driving and undoing all of the above rather than about one capability.

Cleaning up

Every delete this API publishes, what each takes with it, and what refuses.

MCP server

Every operation is also an MCP tool, so an AI agent can drive the same surface.

How it is shaped

Three properties are worth knowing before you write any code, because they apply to the whole surface. Your organization is never something you send. It comes from the credential. There is no organizationId parameter anywhere, and a request that tries to name one is rejected. Every read and write is confined to the organization that owns the credential. Long operations return a job, not a result. Anything that takes more than a few seconds answers 202 with an operation id. You poll one endpoint, GET /v1/operations/{operationId}, for every kind of work. See Operations. Polling is the only completion signal. There are no webhooks today. Each 202 carries a Retry-After telling you how long to wait, and the operation resource carries honest progress.

Get started

Quickstart

Upload a contract and review it, end to end.

Authentication

Create a credential and understand scopes.

Operations

The job envelope every long call returns, and how to poll it well.

Errors

The problem+json shape and what each type means.
Last modified on September 6, 2026