Skip to content

API reference

Rename document

documents.RenameDocumentWriteAPI key

Rename a document without moving it. Documents awaiting signatures cannot be renamed.

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

Access & visibility

Allow documents.RenameDocument 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.

scopestringOptional

The tree the document is in. Omit to take it from the document itself.

Allowed: "org", "user", "resources".

file_idstringRequired

Use a file_id returned by this listing or by CompleteUpload. It is not an upload ID, storage path or filename. documents.ListDocuments.

At least 1 character.

filenamestringRequired

New display filename after trimming surrounding spaces. Include the desired extension for an uploaded file. Renaming does not convert its format or change its bytes.

At least 1 character. At most 255 characters.

Response

Returns 200 OK with a JSON body.

The file stays in the same folder and keeps its file_id. Reading a shared document does not necessarily permit renaming it: the acting member must have authority to administer the document, such as its owner, responsible creator or a permitted workspace administrator. An existing signing lock prevents changes to a document's name.

file_idstringRequired

The same stable identity supplied as file_id. This response uses camelCase; later requests still use file_id.

filenamestringRequired

The resulting trimmed filename. Use this value when updating your display; the file identity has not changed.

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 signing_locked A signing request protects this document from this change. Inspect its signing state in Brigg; completed signed records must not be destroyed.
400 scope_mismatch The supplied scope differs from the document's current collection. Read its location again or omit scope to resolve it from the document.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "scope": {
      "type": "string",
      "enum": [
        "org",
        "user",
        "resources"
      ],
      "description": "The tree the document is in. Omit to take it from the document itself."
    },
    "file_id": {
      "type": "string",
      "minLength": 1,
      "description": "Use a file_id returned by this listing or by CompleteUpload. It is not an upload ID, storage path or filename. [documents.ListDocuments](/developers/reference/documents/ListDocuments)."
    },
    "filename": {
      "type": "string",
      "minLength": 1,
      "maxLength": 255,
      "description": "New display filename after trimming surrounding spaces. Include the desired extension for an uploaded file. Renaming does not convert its format or change its bytes."
    }
  },
  "required": [
    "file_id",
    "filename"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "file_id": "f_agreement",
      "filename": "Signed agreement.pdf"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "file_id": {
      "type": "string",
      "description": "The same stable identity supplied as file_id. This response uses camelCase; later requests still use file_id."
    },
    "filename": {
      "type": "string",
      "description": "The resulting trimmed filename. Use this value when updating your display; the file identity has not changed."
    }
  },
  "required": [
    "file_id",
    "filename"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "file_id": "f_agreement",
      "filename": "Signed agreement.pdf"
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.