Skip to main content
POST
Export a matter summary as PDF or DOCX

Authorizations

Authorization
string
header
required

Workspace credential issued from the automation console at /automation. Send it as Authorization: Bearer vq_ws_.... This is NOT a Data API key: a vq_key_ credential is refused here and names the other product in the error.

Path Parameters

matterId
string
required

mat_ identifier of the matter to work inside. Everything in this API hangs off a matter, and the matter in the path is what the authorization boundary is checked against. Take it from GET /v1/matters.

summaryId
string
required

sum_ identifier of the matter summary. Returned on the operation that generated it.

Body

application/json
format
enum<string>
required

There is no CSV: a summary is a narrative with citations, and flattening it into rows would lose the thing being exported.

Available options:
pdf,
docx
Example:

"pdf"

Response

Successful Response

A rendered summary, returned as bytes rather than as a signed URL.

Same reasoning as the facts and draft exports: the renderer runs on demand and writes no object, so a URL would mean storing client work product first.

format
string
required

The format that was rendered.

Example:

"docx"

filename
string
required

A filename derived from the matter's own name.

Example:

"msa-acme-v3.docx"

sizeBytes
integer
required

Decoded size, so you can check content round-tripped.

Example:

248193

content
string
required

The file, base64-encoded.

Example:

"UEsDBBQABgAIAAAAIQ..."

Last modified on August 23, 2026