@fusebase/fusebase-gate-sdk 2.5.4 → 2.6.1

package/dist/apis/PortalsApi.js

@@ -71,21 +71,6 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
-    /**
-     * Add a block of any palette type to a portal page
-     * Stages a single block of any supported type onto an existing portal page — the universal building block behind the customizer's 'Add new block' palette (no new page or sidebar item is created). Pass pageId (the target page node id from listPortalContent) and type. Supported types: note, content, docs, help, request, meetings, links, files-dashboard, tasks-dashboard, chats-dashboard, flexible. Type-specific fields: note/content require noteId; flexible requires template (e.g. {type:'text'|'image'|'title'|'dashboard'|'app-feature'|...}) and may carry bricks; the link cards (docs/help/request/meetings/links) and others take their fields via the free-form `properties` object (e.g. image/link). It does NOT accept type='projection' — use addPortalLinkedBlock for a Linked block. This op does NOT accept type='embed', a flexible block with template.type='timeline' or a timeline brick (use addPortalTimelineBlock), a flexible block with template.type='dashboard' or a dashboard brick (use addPortalDatabaseBlock), a flexible block with template.type='integration' or an integration brick (use addPortalDynamicTableBlock), a flexible block with template.type='diagram' or a diagram brick (use addPortalBpmnDiagramBlock) or type='chat' — use addPortalEmbedBlock for Embed blocks and addPortalChatBlock for Chat blocks. It also does NOT accept type='files-bucket': use addPortalFileUploaderBlock for File uploader blocks. It does NOT accept type='files-recent': use addPortalRecentFilesBlock for Recent files blocks. It does NOT accept a flexible ai-agent template or an ai-agent brick: use addPortalAiAgentBlock, which binds the agent to the caller. It does NOT accept a flexible `form` template or a `form` brick either: use addPortalFormBlock, which owns the canonical Form block and its fields. It does NOT accept type='info': use addPortalInfoBlock, which owns the canonical Info block, its icon catalog and its destination resolution. It does NOT accept type='task-list' or a note/content block with properties.templateKey='task-list': use addPortalTaskListBlock, which creates the note and its task list. Use addPortalNoteBlock for the common note case or addPortalAppPage for an app on its own page. Note: a `content` block renames the page to its title, so leave title empty for content blocks. The block is staged in the portal's customizer draft (not published immediately); the owner reviews and publishes it. Returns the block id and the draft branch/seqs. Requires portals.write access.
-     */
-    async addPortalBlock(params) {
-        return this.client.request({
-            method: "POST",
-            path: "/:orgId/portals/:portalId/blocks",
-            pathParams: params.path,
-            headers: params.headers,
-            body: params.body,
-            opId: "addPortalBlock",
-            expectedContentType: "application/json",
-        });
-    }
     /**
      * Add a BPMN Diagram block to a portal page
      * Stages one Customizer-compatible BPMN Diagram block on an EXISTING portal page — the programmatic equivalent of the customizer's Experimental "BPMN Diagram" tile. It creates exactly one flexible block with a single BPMN diagram brick; no page, sidebar item or menu icon change comes with it. The diagram is created EMPTY, exactly as the Customizer creates it: the process itself is drawn or imported from a `.bpmn` file in Portal Customizer. BPMN XML, `.bpmn` file uploads, task ids, persisted data/details and links for BPMN Task elements are rejected. This is not a Mermaid diagram, a generic flowchart, a Timeline or an image. The body may be empty, which reproduces the Customizer default: the title "BPMN Diagram", a 500px canvas, a blank backdrop with the title shown, width 6 and automatic height. `title` is the block title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `content.diagramHeight` is the BPMN canvas height in pixels (integer 150-5000, default 500) and is distinct from the block Layout height. `appearance` sets Customizer Backdrop `none`, `blank` or `custom`; a custom backdrop takes a background, padding (default `s`) and `showTitle` (default true). `layout` sets Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px). The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -161,6 +146,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Chat dashboard navigation item
+     * Adds a root navigation item pointing at the portal's system Chat dashboard page (`/chats-dashboard`), staged in the customizer draft. The page and its canonical `chats-dashboard` block are created with the portal, so this operation never creates them: if the portal has no such page the request returns 409 and stages nothing. This is the Customizer's Dashboards > Chat dashboard action, not an ordinary block — the item is always a ROOT item, so the operation takes no `pageId` and no `parentId`. Use addPortalChatBlock instead for a channel or direct-message widget on an existing page. Duplicates are allowed, as in the Customizer: any bar may carry several items, and every one of them points at the same dashboard. The body may be empty, which uses the default title "Chat Dashboard"; `title` is plain text of at most 100 characters and names the navigation item only — the page title, icon and route are managed by the service. `positionType` ('sidebar' default, 'top' or 'footer') picks the root menu bar. Requires portals.write access.
+     */
+    async addPortalChatsDashboardMenuItem(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/chats-dashboard",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalChatsDashboardMenuItem",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Countdown block to a portal page
      * Stages one Customizer-compatible Countdown on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Countdown" tile. It creates exactly one flexible block with a single Countdown item that ticks down days, hours, minutes and seconds to a future moment; no page, sidebar item or external entity is created. The body may be empty, which reproduces the Customizer default: the title "Countdown" and a target 30 days after creation. `content.targetAt` is an absolute RFC 3339 date-time with `Z` or an explicit UTC offset — epoch seconds/milliseconds, a timezone-less local date and a duration are rejected, as are a raw timestamp, brick, renderer style, the item's internal title and its fixed days/hours/min/sec labels. The target must not be in the past or more than 99 days after creation. `title` is the block title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `appearance` sets Customizer Backdrop `none`, `blank` or `custom`; omitting it keeps the canonical blank backdrop with the title shown, and a custom backdrop takes a background, padding (default `s`) and `showTitle` (default true). `layout` sets Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px). The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -236,6 +236,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Files dashboard navigation item
+     * Adds a root navigation item pointing at the portal's system Files dashboard, staged in the customizer draft. If the portal has no `/files-dashboard` page yet, the page and its canonical `files-dashboard` block are created in the same batch; if it already has one, only the item is added, so several bars can link to the same dashboard. The dashboard renders the portal's full File Manager, so it cannot be placed on a page of your choice — the operation takes no `pageId` and no `parentId`. Use addPortalRecentFilesBlock or addPortalFileUploaderBlock instead for a file list or an upload area on an existing page. Pass `positionType` to choose the bar: 'sidebar' (default), 'top' (topbar) or 'footer'. The body may be empty, which uses the default title "Files"; `title` is plain text of at most 100 characters and names the navigation item (and the dashboard block when it is created) — the page title, route and icon are managed by the service. Requires portals.write access.
+     */
+    async addPortalFilesDashboardMenuItem(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/files-dashboard",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalFilesDashboardMenuItem",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a File uploader block to a portal page
      * Stages one Customizer-compatible File uploader on an EXISTING portal page — the programmatic equivalent of the customizer's File management "File uploader" tile. It creates an EMPTY upload area (internally a `files-bucket` block) that non-visitor portal users can upload files to and manage; no page, sidebar item, bucket or file is created and nothing is uploaded. The body may be empty, which reproduces the Customizer default: the title "File uploader", no description and both file columns hidden. `title` is plain text and `description` is a plain-text hint of at most 50 characters. `showAuthor` and `showUploadDate` add the matching file-list columns; neither changes who may upload — that stays a function of the viewer's portal role. `layout` sets Width (3, 4 or 6, default 3) and Height (Auto by default, a manual value is at least 50px). The screen has no Appearance section, so `appearance`, `rowspan`, upload permissions, bucket/file ids and query/sort/limit are not accepted. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -326,6 +341,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add an existing Internal Space page to a portal
+     * Adds an EXISTING Internal Space page (Fusebase note) to the portal as its own page — the 'Internal Space Content' tile of the customizer. Identify the note with either noteId (its global id) or noteUrl (the browser URL, e.g. https://acme.nimbusweb.me/space/<workspaceId>/page/<noteId>); exactly one is required. The note must already exist in the portal's workspace — use createPortalPageWithNote to create a NEW note instead, or addPortalNoteBlock to embed a note as one more block on an existing page. The page (page node + note menu item + content block) is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it — the note is shared into the portal at publish time. `title` names the page and its menu item; the block header always shows the note's own title, because publishing backfills it from the note's share. Everything defaults to the note's title when `title` is omitted. Pass parentId to nest the page under an existing folder, or positionType ('sidebar' default, 'top', 'footer') to place a root page in a specific menu bar. Returns the note/page/menu-item/block ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     */
+    async addPortalInternalSpacePage(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/internal-space",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalInternalSpacePage",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Kanban board as a block to a portal page
      * Creates a new Fusebase note, shares it into the portal, initialises a Kanban board inside it and adds the note as a block to an existing portal page — the programmatic equivalent of the customizer's Project management "Kanban" tile. No new page and no sidebar menu item is created. For a published page resolve pageId from listPortalContent; for a page created earlier in the active draft use the pageId that operation returned. Optional body: title (block, note and board title, non-empty and at most 100 characters, default "Kanban") and columns (1-10 column titles in order, each at most 100 characters, default "To do", "In progress", "Done"). The board starts empty — tasks are added by portal users, not by this operation. Use addPortalBlankNoteBlock when an empty note is wanted instead. The block is appended after the last block of the page body and is staged in the portal's customizer draft (not published immediately). Returns the note/board/block ids and the draft branch/seqs. Requires portals.write access.
@@ -401,6 +431,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Tasks dashboard navigation item
+     * Adds a root navigation item pointing at the portal's system Tasks dashboard, staged in the customizer draft. If the portal has no `/tasks-dashboard` page yet, the page and its canonical `tasks-dashboard` block are created in the same batch; if it already has one, only the item is added, so several bars can link to the same dashboard. The dashboard shows each viewer the portal tasks they are allowed to see, so it cannot be placed on a page of your choice — the operation takes no `pageId` and no `parentId`. Use addPortalTaskListBlock or addPortalKanbanBlock instead for a task list or board on an existing page. Pass `positionType` to choose the bar: 'sidebar' (default), 'top' (topbar) or 'footer'. The body may be empty, which uses the default title "Task Dashboard"; `title` is plain text of at most 100 characters and names the navigation item (and the dashboard block when it is created) — the page title, route and icon are managed by the service. Requires portals.write access.
+     */
+    async addPortalTasksDashboardMenuItem(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/tasks-dashboard",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalTasksDashboardMenuItem",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Text & Media Simple text block to a portal page
      * Stages one Customizer-compatible Simple text block on an existing portal page — the programmatic equivalent of the customizer's Text & Media "Simple text" tile. `content` carries the text settings (plain text, one palette colour token such as `cyan-700` — never HEX or CSS —, size `s`/`m`/`l`/`xl`, a unique set of `bold`, `italic`, `underline`, `lineThrough` styles and alignment). `appearance` is the Customizer Appearance section; a `custom` backdrop takes a colour, gradient or one of the five preset background images (`azure`, `mira`, `solis`, `serenity`, `glow`) — an image URL, asset id or upload is rejected. HTML, Markdown, CSS, Tailwind classes, a wrapper title and raw bricks are not accepted. Defaults: text "Your journey starts here! Add your unique message to engage your audience.", size `m`, no styles, left alignment and a blank backdrop. It creates exactly one flexible block on an EXISTING page; no page, sidebar item or media asset is created. `layout` sets Customizer Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px); `rowspan`, row placement and responsive values are not part of this contract. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -521,6 +566,34 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Remove a block from a portal page
+     * Removes ONE existing removable block from a portal page and STAGES the deletion in the active customizer draft; the live portal only changes when the draft is published. Takes no body. It deletes the portal block ONLY — the backing Fusebase note, Kanban board, task list, app, agent, database/dashboard source and files are kept. Resolve the exact pageId and blockId with listPortalPageBlocks first and let the user choose when several blocks may match. Requires portals.write access.
+     */
+    async deletePortalBlock(params) {
+        return this.client.request({
+            method: "DELETE",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId",
+            pathParams: params.path,
+            headers: params.headers,
+            opId: "deletePortalBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Delete a portal menu item
+     * Deletes a portal menu item (folder, page, or link) identified by itemId. Deleting a folder removes its whole subtree, including items created in the same draft. The portal's home item cannot be deleted. The item may be a published one (from listPortalContent) or one that exists only in the active draft, by the exact id its create operation returned. The deletion is staged in the portal's customizer draft (not published immediately): the owner reviews and publishes it, and a concurrent customizer edit returns 409 — retry the request. Requires portals.write access.
+     */
+    async deletePortalItem(params) {
+        return this.client.request({
+            method: "DELETE",
+            path: "/:orgId/portals/:portalId/items/:itemId",
+            pathParams: params.path,
+            headers: params.headers,
+            opId: "deletePortalItem",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Duplicate an existing portal
      * Creates a new portal as a full copy of an existing portal: settings, theme, menu structure, pages, and content blocks are all copied. Returns portal details. Status is 'ready' immediately for P_SUB domains; 'pending' for custom/CNAME domains or if content copy is still in progress. Requires org.write access.
@@ -565,6 +638,20 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Read one portal block's current settings
+     * Read-only step between listPortalPageBlocks and a typed updatePortal*Block operation: shows what the block is set to TODAY so the change can be confirmed with the user before it is staged. Reads the published portal AND its active customizer draft. Returns the block's semantic `kind` — the vocabulary the typed updates use, which neither `type` nor `templateType` gives on its own — plus `title`, `place`, `layout`, `editOperation` and the kind-specific `settings`. `settings` and `editOperation` are null for a kind whose typed update operation does not exist yet; call listPortalPageBlocks first to resolve the blockId. Internal customizer state (bricks, wrappers, share keys, draft events) is never returned. Requires portals.write access.
+     */
+    async getPortalBlock(params) {
+        return this.client.request({
+            method: "GET",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId",
+            pathParams: params.path,
+            headers: params.headers,
+            opId: "getPortalBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Count matching blocks on a portal page (published + draft)
      * Universal preflight: how many active blocks of a given type a page already carries, counted over the published portal AND its active customizer draft — so a block staged earlier in this session is included. `type` is a canonical portal block type; `templateType` is allowed only with type='flexible' and narrows by the flexible template (e.g. type='flexible' + templateType='ai-agent' for AI Agent blocks). Returns only the count — never blocks, bricks, ids or draft events. Requires portals.write access.
@@ -697,6 +784,20 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * List the blocks of a portal page
+     * Read-only discovery step before movePortalBlock, deletePortalBlock and the typed block updates. Lists EVERY block of ONE page over the published portal AND its active customizer draft, in display order, as `blocks` of `blockId`, `type`, `templateType`, `title`, `editOperation`, `place` and `draftOnly`. The order is the page order — area (`place`) first, then position inside it — and is what a move anchor refers to; a move anchor must share the block's `place`. `editOperation` names the typed update operation for the block, or is null when its kind has none yet. Unlike listPortalLinkableBlocks this includes Linked blocks, because they can be moved and deleted. The response carries identity only: never bricks, wrappers, content, data or draft events. Requires portals.write access.
+     */
+    async listPortalPageBlocks(params) {
+        return this.client.request({
+            method: "GET",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks",
+            pathParams: params.path,
+            headers: params.headers,
+            opId: "listPortalPageBlocks",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * List organization portals
      * Returns portals visible for the caller in the organization. Requires portals.read and org access.
@@ -711,6 +812,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Move a block within its portal page
+     * Reorders ONE existing block on its own portal page and STAGES the change in the active customizer draft; nothing is published. Send exactly one position: `{position:"first"}`, `{position:"last"}`, `{beforeBlockId}` or `{afterBlockId}`. An anchor block must be on the same page, in the same area, and cannot be the block being moved. A raw index and the internal append sentinel 999 are rejected — the index is resolved server-side against the effective state, so a concurrent draft change cannot land the block in the wrong slot. Resolve ids with listPortalPageBlocks first. Moving to another page or changing the block's area is not supported. Requires portals.write access.
+     */
+    async movePortalBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/position",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "movePortalBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Publish an entire portal draft after user confirmation
      * Publishes every staged change in the portal's customizer draft to the live portal, including changes the owner or another user staged manually. Never call this operation automatically after staging content or settings. Before every call, tell the user that the entire pending draft will go live, ask one clear yes/no question, and wait for explicit confirmation. Do not infer publish permission from a content-edit request or successful staging. Confirmation is single-use and applies only to the current draft and one attempt. Returns 400 if the draft is empty and 409 if the portal was published elsewhere since the draft was based; obtain new confirmation before retrying. Requires portals.write access.
@@ -769,6 +885,141 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Update a portal AI Agent block
+     * Changes the exact agent used by one AI Agent block and synchronizes its title. Use listPortalAiAgents first.
+     */
+    async updatePortalAiAgentBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/ai-agent",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalAiAgentBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal App block
+     * Updates the title or complete published-app identity of one existing App block. Binding changes require productId, appId, productType and productOrgId together.
+     */
+    async updatePortalAppBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/app",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalAppBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal BPMN Diagram block
+     * Edits ONE existing BPMN Diagram block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one of `title`, `content.diagramHeight`, `appearance` or `layout` must be sent. `diagramHeight` is the BPMN canvas height inside the block, from 150 to 5000 pixels; `layout.height` is the separate outer block height. This operation cannot accept BPMN XML, import a `.bpmn` file, or edit process elements and links. Title is plain text and supports only {{ClientName}} and {{ClientLastName}}. Appearance is a complete variant. Layout width is 2 to 6 and manual height is at least 50; null restores automatic height. Call getPortalBlock first for current settings. Rejected with 400: an empty patch, invalid canvas/layout/appearance, unsupported variables, a block of another kind, and a patch the block already satisfies. Requires portals.write access.
+     */
+    async updatePortalBpmnDiagramBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/bpmn-diagram",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalBpmnDiagramBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Card block
+     * Edits ONE existing Card block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one field must be sent. Editable: `view` (Card Type), `content` (image, heading, description, button and the shared destination), `appearance` and `layout` (`colspan` 2 to 6, `height` at least 50 or null for the automatic height). Each `content` item is a complete variant: a heading sent with only `size` keeps its stored text, styles and alignment, and `{ visible: false }` may carry nothing else — but re-showing an item with `{ visible: true }` keeps everything it had. `destination` is the Card's single link, shared with its Button; `null` removes it. Changing `view` repaints the text colours the way the Customizer does, unless an explicit `color` is sent with it. Call getPortalBlock first to see the current values — it reports no `appearance` for a Card still on its original wrapper, which is not a backdrop the update can ask for. Rejected with 400: an empty patch, text or styles next to a hidden item, a destination page outside this portal, a colour outside the Tailwind palette, background, padding or showTitle outside backdrop `custom`, a value outside the supported range, a block of another kind, and a patch the block already satisfies — the message names which. Requires portals.write access.
+     */
+    async updatePortalCardBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/card",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalCardBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Card group block
+     * Updates title, description, the full desired list of 1 to 6 cards, appearance or layout. Each card accepts plain title text, one built-in image and a same-portal page, absolute HTTPS URL, email or null destination. Image URLs, uploads, raw links, bricks and item indexes are never accepted.
+     */
+    async updatePortalCardGroupBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/card-group",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalCardGroupBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Carousel block
+     * Edits ONE existing Carousel block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: `layout` is a field-level patch, while `content.items`, when sent, is the FULL desired list of 1 to 6 slides in visual order. Each slide may contain `caption`, `description`, `button: { text }` or null, and `destination` or null. The slide surface and Button share one destination. Description supports only {{ClientName}} and {{ClientLastName}}; caption and Button text support no variables. Images remain the block's built-in images. Do not send media, autoplay, duration, controls, indicators, appearance or item ids. Layout width is 2 to 6 and manual height is at least 50; null restores automatic height. Call getPortalBlock first for the current full list. Rejected with 400: an empty patch, an invalid list or destination, unsupported variables, a block of another kind, and a patch the block already satisfies. Requires portals.write access.
+     */
+    async updatePortalCarouselBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/carousel",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalCarouselBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Chat block
+     * Updates title, exact channel/DM target, channel membership restriction or layout of one Chat widget. Use listPortalChatChannels or listPortalChatUsers before changing its target.
+     */
+    async updatePortalChatBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/chat",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalChatBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Set who may open one portal page or folder
+     * Replaces or extends the client-facing access list of one published portal page or folder selected by its exact full path. mode='replace' removes the previous item ACL and leaves access to the supplied emails; mode='add' preserves existing access and adds the supplied emails. Missing portal members receive a targeted client/editor portal invitation without being granted access to other private items. Folder permissions cascade to all descendants. mode='add' on an item that is open to everyone is a successful no-op — the users already have access and the item is not made private. The change is applied immediately and must not be followed by publishPortalDraft. Requires portals.manage access.
+     */
+    async updatePortalContentPermissions(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/content/permissions",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalContentPermissions",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Countdown block
+     * Edits ONE existing Countdown block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one of `title`, `content.targetAt`, `appearance` or `layout` must be sent. `targetAt` is an absolute RFC 3339 date-time with Z or an explicit UTC offset; it must not be in the past or more than 99 days from the update. Never send epoch time, a timezone-less date, duration or internal countdown items. Title is plain text and supports only {{ClientName}} and {{ClientLastName}}. Appearance is a complete variant. Layout width is 2 to 6 and manual height is at least 50; null restores automatic height. Call getPortalBlock first for the current settings. Rejected with 400: an empty patch, invalid target, unsupported variables, invalid appearance/layout, a block of another kind, and a patch the block already satisfies. Requires portals.write access.
+     */
+    async updatePortalCountdownBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/countdown",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalCountdownBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Update portal custom CSS/JS code
      * Sets custom code for the portal: css (custom styles), headCode (HTML/JS at the start of <head>), and bodyCode (HTML/JS at the end of <body>). css is auto-scoped under the portal root container #main-scrolling-container so it cannot leak into the customizer UI; scope selectors accordingly and avoid body/html/:root. Only the provided fields change; omitted fields keep their current value, and an empty string clears a field. At least one field is required. Custom code only renders on portals served from a custom CNAME domain. The change is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending change, and publishes it. Returns the draft branch/seq. Requires portals.write access.
@@ -784,5 +1035,275 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Update a portal Custom widget block
+     * Updates title, the full desired semantic brick list, appearance or layout of one existing Custom widget. Supported bricks are heading, text, built-in image, avatar, rating, link and button. Raw brick ids, indexes, image sources, classes and links are never accepted.
+     */
+    async updatePortalCustomWidgetBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/custom-widget",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalCustomWidgetBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Database block
+     * Edits ONE existing Database block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one field must be sent. Editable: `target`, `title`, `itemsPerPage` (10, 20, 50, 100, 200 or 500), `appearance` and `layout` (`colspan` 2 to 6, `height` at least 50 or null for the automatic height). `target` and `appearance` are NOT field-level patches: each is a complete variant when sent. Call listPortalDatabaseBlockSources for a new target and use the exact `databaseId`, `dashboardId` and `viewId` chain it returns; the whole chain is re-validated as the calling user. Call getPortalBlock first to see the current values — it reports no `databaseId`, because the block does not store one. Rejected with 400: an empty patch, an incomplete target variant, a dashboard or view the caller cannot read, a colour outside the Tailwind palette, background, padding or showTitle outside backdrop `custom`, a value outside the supported range, a block of another kind, and a patch the block already satisfies — the message names which. Requires portals.write access.
+     */
+    async updatePortalDatabaseBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/database",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalDatabaseBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Dynamic Table block
+     * Edits ONE existing Dynamic Table block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one of `title`, `appearance` or `layout` must be sent. This operation does not configure or replace the integration provider, OAuth connection, data source, columns or rows. Title is plain text and supports only {{ClientName}} and {{ClientLastName}}. Appearance is a complete variant. Layout width is 2 to 6 and manual height is at least 50; null restores automatic height. Call getPortalBlock first for the current settings. Rejected with 400: an empty patch, unsupported variables, invalid appearance/layout, a block of another kind, and a patch the block already satisfies. Requires portals.write access.
+     */
+    async updatePortalDynamicTableBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/dynamic-table",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalDynamicTableBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Embed block
+     * Edits ONE existing Embed block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one field must be sent. Editable: `title`, `embedType`, `url` or `content`, `showEmbedLink`, `colspan` (2 to 6), `rowspan` (1 to 4) and `height` (a positive number, or null for the automatic height). The SOURCE is not a field-level patch: `embedType` plus exactly one of `url` (named variants) or `content` (`custom`) is a complete variant, so changing the type requires sending the matching source in the same request, and `embedType` alone is rejected. Call getPortalBlock first to see the current values. Rejected with 400: an empty patch, a url on a `custom` embed or content on a named one, a non-external or malformed url, embed code with no supported construct, a value outside the supported range, a block of another kind, and a patch the block already satisfies — the message names which. Requires portals.write access.
+     */
+    async updatePortalEmbedBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/embed",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalEmbedBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal File uploader block
+     * Updates title, short description, Author/Upload date visibility or layout of one existing File uploader block. It does not expose storage, permissions, bucket/file ids, query, sort, limit, appearance or rows.
+     */
+    async updatePortalFileUploaderBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/file-uploader",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalFileUploaderBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Form block
+     * Updates title, description, form fields/submit/reusable settings, appearance or layout. Fields are a full desired list: preserve existing fieldId values and omit fieldId only for new fields. A non-reusable Form with response data cannot change fields or submit controls. Response data, brick ids and indexes are never accepted.
+     */
+    async updatePortalFormBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/form",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalFormBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Heading block
+     * Edits ONE existing Text & Media Heading block and STAGES the change in the active customizer draft; nothing is published. Editable: `content` (text, colour, size, styles, alignment), `appearance` and `layout`. The block's wrapper title, HTML, CSS, image url and raw bricks are not accepted. This is a PATCH: an omitted field keeps its current value, and at least one field must be sent. `content` is a field-level patch — a size, style or alignment left out keeps what the block has today. `appearance` is NOT: it is a discriminated variant and must be sent complete, so read the current one with getPortalBlock first; under backdrop `custom` an omitted `background` keeps the block's current one, which is what getPortalBlock reports for a block still on the portal theme's surface colour. `layout.colspan` is 2 to 6 and `layout.height` is at least 50, or null for the automatic height. Rejected with 400: an empty patch, a block of another kind, and a patch the block already satisfies — the message names which. Requires portals.write access.
+     */
+    async updatePortalHeadingBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/heading",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalHeadingBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update portal homepage settings
+     * Sets the portal's Homepage settings, the same panel the customizer shows: title (renames the Home menu item and the homepage itself) and the sidebar toggles showSidebarOnOtherPages, showSidebarOnHomePage and expandSidebarByDefault. Only the provided fields change; omitted fields keep their current value. The change is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending change under Homepage settings, and publishes it. Returns the draft branch and the seqs of the staged events. Requires portals.write access.
+     */
+    async updatePortalHomepage(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/homepage",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalHomepage",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal HTML/CSS block
+     * Updates title, a partial raw HTML/CSS/JavaScript content patch or layout of one existing HTML/CSS block. The portal must use a verified custom CNAME domain. Omitted code fields remain unchanged and an empty string clears one field.
+     */
+    async updatePortalHtmlCssBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/html-css",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalHtmlCssBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Image block layout
+     * Edits the LAYOUT of one existing Text & Media Image block and STAGES the change in the active customizer draft; nothing is published. The picture stays the Customizer's built-in image — an image url, asset id, upload, base64, local path, filename, content or appearance is rejected. `layout.colspan` is 2 to 6 and `layout.height` is at least 50, or null for the automatic height. Rejected with 400: an empty patch, a block of another kind, and a patch the block already satisfies. Requires portals.write access.
+     */
+    async updatePortalImageBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/image",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalImageBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Info block
+     * Updates title, a complete semantic image or destination variant, new-tab behavior or layout of one existing Info block. Icon images require an exact id returned by searchPortalInfoBlockIcons. Raw persisted image/link values, wrappers and indexes are never accepted.
+     */
+    async updatePortalInfoBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/info",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalInfoBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal menu item
+     * Updates an existing portal menu item (folder, page, or link) identified by itemId. Supports rename (name), icon, visibility (visible), reorder within a bar (index), moving between bars (positionType: sidebar/top/footer), and re-parenting (parentId, '' = root). Re-parenting is rejected (400) if parentId is the item itself, one of its descendants, or an item that cannot hold children (only a folder, note, section, process or page can — a link, dashboard, tag list or the home item is rejected), and 404s if the parent is not in the menu. A re-parented item moves to its parent's bar along with its whole subtree, so a positionType passed alongside parentId must match the parent's bar (400 otherwise). Pass only the fields to change; at least one is required. The item may be a published one (from listPortalContent) or one that exists only in the active draft — use the exact menuItemId/folderId returned by createPortalPage, createPortalPageWithNote, createPortalFolder or createPortalLink. The same holds for parentId. The change is staged in the portal's customizer draft (not published immediately): the owner reviews and publishes it, and a concurrent customizer edit returns 409 — retry the request. Requires portals.write access.
+     */
+    async updatePortalItem(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/items/:itemId",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalItem",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Linked block
+     * Changes the exact source of ONE existing Linked block and stages the change. Resolve the source page with listPortalContent, then use the exact source from listPortalLinkableBlocks. Both portals must be in the same organization and editable by the caller. A cross-portal source must be published. Linked blocks cannot reference another Linked block or a source on their own target page. Title, content, appearance and layout are mirrored and cannot be supplied.
+     */
+    async updatePortalLinkedBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/linked",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalLinkedBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a note-backed portal block
+     * Edits ONE existing note-backed block — the kind behind addPortalNoteBlock, addPortalBlankNoteBlock, addPortalKanbanBlock and addPortalTaskListBlock, which all persist as the same block kind — and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one field must be sent. Editable: `title`, `layout.colspan` (3, 4, 5 or 6) and `layout.height` (at least 50, or null for the automatic height). The block's CONTENT is not editable here — the note's text, the Kanban board and the task list belong to their own operations, and noteId/workspaceId are the block's identity. Call getPortalBlock first to see the current values and confirm the change. Rejected with 400: an empty patch, a colspan or height outside the supported range, a block of another kind, and a patch the block already satisfies — the message names which. Requires portals.write access.
+     */
+    async updatePortalNoteBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/note",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalNoteBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Recent files block
+     * Edits ONE existing Recent files block and STAGES the change in the active customizer draft; nothing is published. This is a PATCH: an omitted field keeps its current value, and at least one of `title`, `source` or `layout` must be sent. Source is either the entire portal or one exact page in the same portal; resolve that page first with listPortalContent. The operation cannot change sort order, the five-item limit, offset, file type, other query data or appearance. Width is 3, 4, 5 or 6 and manual height is at least 50; null restores automatic height. Call getPortalBlock first for the current settings. Requires portals.write access.
+     */
+    async updatePortalRecentFilesBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/recent-files",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalRecentFilesBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update portal branding
+     * Sets the portal's branding, the same fields the customizer's Portal style panel writes: the color theme, the header logo and the favicon. Only the provided fields change; omitted fields keep their current value. Colors come from the named themes — arbitrary hex colors and web fonts are not part of the portal theme model; use updatePortalCustomCode for those. The change is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending change and publishes it. Returns the draft branch and the seq of the staged event. Requires portals.write access.
+     */
+    async updatePortalStyle(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/style",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalStyle",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Simple text block
+     * Edits ONE existing Text & Media Simple text block and STAGES the change in the active customizer draft; nothing is published. Editable: `content` (text, colour, size, styles, alignment), `appearance` and `layout`. The block's wrapper title, HTML, CSS, image url and raw bricks are not accepted. This is a PATCH: an omitted field keeps its current value, and at least one field must be sent. `content` is a field-level patch — a size, style or alignment left out keeps what the block has today. `appearance` is NOT: it is a discriminated variant and must be sent complete, so read the current one with getPortalBlock first; under backdrop `custom` an omitted `background` keeps the block's current one, which is what getPortalBlock reports for a block still on the portal theme's surface colour. `layout.colspan` is 2 to 6 and `layout.height` is at least 50, or null for the automatic height. Rejected with 400: an empty patch, a block of another kind, and a patch the block already satisfies — the message names which. Requires portals.write access.
+     */
+    async updatePortalTextBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/text",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalTextBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Update a portal Timeline block
+     * Updates view, title, content, appearance or layout of one existing Timeline. content.steps is the full desired visual-order list of 1..6 steps; completed steps must form one prefix. Internal destinations use exact same-portal page ids.
+     */
+    async updatePortalTimelineBlock(params) {
+        return this.client.request({
+            method: "PATCH",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/:blockId/timeline",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "updatePortalTimelineBlock",
+            expectedContentType: "application/json",
+        });
+    }
 }
 exports.PortalsApi = PortalsApi;