Skip to main content
GET
Get a legal document

Path Parameters

document_key
string
required

Document identifier, e.g. dakota_tos.

Query Parameters

version
string

A specific published revision. Omit for the revision in force now.

Response

The requested revision.

One published revision of a legal document.

A revision is IMMUTABLE: version identifies an exact text, and that text never changes once published. Correcting a document produces a new revision rather than editing an existing one, so an acceptance recorded against a version always refers to the same words.

key
string
required

Stable identifier for the document across all its revisions.

Example:

"dakota_tos"

version
string
required

The published revision identifier, taken from the document itself. Treat it as opaque — do not parse or compare it for ordering.

Example:

"2026-07-23"

revision
integer
required

Monotonic ordinal within key. Unlike version, this is ordered: a higher number is a later revision.

Example:

4

content_type
string
default:text/markdown
required

Media type of content.

Example:

"text/markdown"

title
string
Example:

"Dakota Terms of Service"

content
string

The document text, in content_type format. Render this to your customer before capturing acceptance.

Present when a single document is fetched by key. OMITTED from the GET /legal/documents index, which carries identity and revision only — fetch the document you intend to display.

Example:

"This Platform Services Agreement (the \"Agreement\")…"

content_url
string

Where the document is published for humans to read.

Example:

"https://dakota.xyz/terms"

effective_date
string

The date printed inside the document — what the customer reads as "Last Updated". Show this alongside the text.

Absent for imported historical revisions whose stated date could not be established.

Example:

"2026-07-23"