Save live content

Consolidate a live document's pending edits into a durable snapshot, export it to storage and enqueue fact re-extraction (the extraction itself runs asynchronously). Pass state_update with the client's current Yjs state so the snapshot includes edits still buffered in the collaboration service. Use a fresh idempotency_key per save.

Authorization

bearerApiKey

AuthorizationBearer <token>

Create a scoped API key in the Adlass settings.

In: header

Path Parameters

document_id*string

Resource identifier: document_id.

Formatuuid

Header Parameters

X-Request-Id?string

Optional correlation identifier.

Lengthlength <= 128

Idempotency-Key*string

A unique key for this intended write. Reuse it only for an identical retry.

Length1 <= length <= 200

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

state_update?string

Optional: the saving client's complete Yjs document state (Y.encodeStateAsUpdate) as base64, at most 4 MiB decoded. Include it so the save contains every edit visible to the user at that moment, including edits the collaboration service has not forwarded yet.

Lengthlength <= 6291456

Response Body

`application/json`

`application/problem+json`

curl -X POST "https://example.com/documents/123e4567-e89b-42d3-a456-426614174000/content/save" \  -H "Idempotency-Key: 123e4567-e89b-42d3-a456-426614174000" \  -H "Content-Type: application/json" \  -d '{}'

{  "document_id": "123e4567-e89b-42d3-a456-426614174000",  "saved_at": "2026-09-04T12:00:00Z",  "extraction_requested": false,  "client_state_included": false}

Authorization

Path Parameters

Header Parameters

Request Body

Response Body

200application/json

400application/problem+json

401application/problem+json

402application/problem+json

403application/problem+json

404application/problem+json

405application/problem+json

409application/problem+json

410application/problem+json

413application/problem+json

415application/problem+json

422application/problem+json

429application/problem+json

500application/problem+json

502application/problem+json

503application/problem+json

504application/problem+json

`application/json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`

`application/problem+json`