Skip to content

API reference

Checkpoint text document

documents.CheckpointTextDocumentWriteAPI key

Save a named version of a text document's current content.

POST/v1/operations/documents.CheckpointTextDocument
On this page

Access & visibility

Allow documents.CheckpointTextDocument on your API key.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

file_idstringRequired

Use the file_id of a collaborative text document. Find an existing document with ListDocuments and select kind=text_document. An uploaded PDF, Word file or plain-text file is not a collaborative text document. documents.CreateTextDocument.

At least 1 character.

labelstringRequired

Name for this saved point, trimmed before saving. Use a meaningful label such as Before legal review.

At least 1 character. At most 120 characters.

Work with text and saved versions

All documents use a stable file_id. Select document_kind=text_document from the listing for these collaborative text operations. Read text document returns its current Markdown and location.

For an exact change, use Edit text document with the existing text and its replacement; this avoids sending an old full copy over another edit. Replace text document replaces the entire Markdown body. Send the read response’s revision as expected_revision to refuse intervening changes atomically. Re-read before resolving a failed match or revision conflict.

A saved version_id identifies historical content. List versions before reading or reverting one, and use Checkpoint text document when you need a named saved point. A revert changes current content; it is not just a historical read.

Response

Returns 200 OK with a JSON body.

version_idstring or nullRequired

ID of the named snapshot of the current live content. Named checkpoints create a history entry even when the text has not changed. The nullable contract also covers a document disappearing during the save; if null, read the document and its history before claiming a named checkpoint was created.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying. Reuse the original Idempotency-Key.
409 not_text_document This file is not a collaborative text document. Use CreateTextDocument or select kind=text_document from ListDocuments.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "file_id": {
      "type": "string",
      "minLength": 1,
      "description": "Use the file_id of a collaborative text document. Find an existing document with [ListDocuments](/reference/documents/ListDocuments) and select kind=text_document. An uploaded PDF, Word file or plain-text file is not a collaborative text document. [documents.CreateTextDocument](/reference/documents/CreateTextDocument)."
    },
    "label": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "Name for this saved point, trimmed before saving. Use a meaningful label such as Before legal review."
    }
  },
  "required": [
    "file_id",
    "label"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "file_id": "f_project_notes",
      "label": "Before legal review"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "version_id": {
      "type": [
        "string",
        "null"
      ],
      "description": "ID of the named snapshot of the current live content. Named checkpoints create a history entry even when the text has not changed. The nullable contract also covers a document disappearing during the save; if null, read the document and its history before claiming a named checkpoint was created."
    }
  },
  "required": [
    "version_id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "version_id": "tdv_project_notes_2"
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.