Skip to main content
POST
Export the chronology 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.

Body

application/json

A POST, because the filters live in the body.

The export honours exactly the filters the list accepts, and it refuses rather than truncating: over the ceiling you get a 413 carrying limit and requested so you can narrow the date range. The web app's export silently stops at 50,000 events with no flag on the response, which hands a customer a file they believe is complete.

format
enum<string>
required

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

Available options:
csv,
pdf,
docx
Example:

"csv"

filters
ChronologyFilters · object

Same fields as the list. Omit for the whole timeline.

Response

Successful Response

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

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

eventCount
integer
required

How many events the file contains. Never truncated.

Example:

1

Last modified on August 23, 2026