Skip to content

API reference

Rename content

documents.RenameBundleWriteMember delegation

Rename an app, website, newsletter, document or template identified by content_id. Requires authority to administer that item. Does not change its ID or existing links.

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

Access & visibility

Allow documents.RenameBundle on your API key.

Acting member required. Send Brigg-Act-As with an approved member account ID. The key supplies permissions; the member selects whose data is used.

The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.

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.

content_idstringRequired

Use content_id and check kind before choosing the operation. An app, template, website and uploaded file are not interchangeable. workspace.ListBundles.

At least 1 character.

namestringOptional

New content display name. Omit to keep the name when changing only icon_slug.

At least 1 character. At most 80 characters.

icon_slugstring or nullOptional

A sidebar icon from the curated catalog; null resets it to the derived default.

Response

Returns 200 OK with a JSON body.

This changes the name or icon of content selected from ListBundles. It preserves content_id and does not copy, move or republish the content. The acting member must be allowed to administer it.

okbooleanRequired

Whether the action completed successfully.

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. Supply Brigg-Act-As with a member authorized by the key’s delegation grant. The selected member must be active and approved by the credential. This selects whose private data is used; the credential supplies permissions. Private ownership and project boundaries still apply.
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.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "content_id": {
      "type": "string",
      "minLength": 1,
      "description": "Use content_id and check kind before choosing the operation. An app, template, website and uploaded file are not interchangeable. [workspace.ListBundles](/developers/reference/workspace/ListBundles)."
    },
    "name": {
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "description": "New content display name. Omit to keep the name when changing only icon_slug."
    },
    "icon_slug": {
      "anyOf": [
        {
          "type": "string",
          "enum": [
            "default",
            "home",
            "users",
            "shield",
            "trophy",
            "headphones",
            "briefcase",
            "award",
            "building",
            "scale",
            "rocket",
            "calendar",
            "checklist",
            "folder",
            "graph",
            "lightbulb",
            "money",
            "package",
            "phone",
            "puzzle",
            "star",
            "tag",
            "cloud",
            "globe",
            "clock",
            "receipt",
            "book",
            "chat",
            "funnel",
            "kanban",
            "ticket"
          ]
        },
        {
          "type": "null"
        }
      ],
      "description": "A sidebar icon from the curated catalog; null resets it to the derived default."
    }
  },
  "required": [
    "content_id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "content_id": "c_vendor_portal",
      "name": "Supplier portal"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "Whether the action completed successfully."
    }
  },
  "required": [
    "ok"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "ok": true
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.