Skip to main content
POST
Export a fact set as CSV, 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.

factSetId
string
required

fct_ identifier of the fact set. Returned on the operation that generated it.

Body

application/json
format
enum<string>
required

csv for a spreadsheet, pdf or docx for a document.

Available options:
csv,
pdf,
docx
Example:

"csv"

Response

Successful Response

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

The renderers run on demand and write no object, so vending a URL would mean writing client work product to storage first. Encryption is on in every deployment, which leaves a choice between an object the customer cannot decrypt and plaintext in the bucket. Same reasoning as the draft export.

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..."

factCount
integer
required

How many facts the file contains.

Example:

1

Last modified on August 23, 2026