@fusebase/fusebase-gate-sdk 2.5.1-sdk.1 → 2.5.1-sdk.2

package/dist/apis/PortalsApi.js

@@ -73,7 +73,7 @@ class PortalsApi {
     }
     /**
      * 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, info, docs, help, request, meetings, links, task-list, projection, files-dashboard, tasks-dashboard, chats-dashboard, files-recent, files-bucket, flexible. Type-specific fields: note/content require noteId; flexible requires template (e.g. {type:'text'|'image'|'title'|'code'|'form'|'dashboard'|'app-feature'|...}) and may carry bricks; info/projection/task-list and others take their fields via the free-form `properties` object (e.g. image/link, sourcePortalId/sourcePageId/sourceBlockId, taskListIds). This op does NOT accept type='embed', a flexible block with template.type='dashboard' or a dashboard brick (use addPortalDatabaseBlock) or type='chat' — use addPortalEmbedBlock for Embed blocks and addPortalChatBlock for Chat blocks — and it does NOT accept a flexible ai-agent template or an ai-agent brick: use addPortalAiAgentBlock, which binds the agent to the caller. 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.
+     * 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, files-recent, 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) 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 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({
@@ -101,6 +101,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Card group block to a portal page
+     * Stages one Customizer-compatible Card group on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Card group" tile, a row of small linked cards. It creates exactly one flexible block with a Description brick and the cards; no page, sidebar item or media asset is created. `content.items` holds 1 to 6 cards, each with a `title` (the caption, plain text without dynamic variables), an optional `image` naming one of the four built-in tile images (`calendar`, `book`, `pen`, `briefcase` — an url, upload, asset id or local path is rejected) and an optional `destination`: an exact `pageId` of a page in THIS portal, an absolute https URL or an email address; omitting it keeps the template link of that card position and an explicit `null` leaves the card without a link. Omitting `content.items` reproduces the Customizer's four template cards. `content.description` is the text above the cards (`visible: false` hides it, otherwise plain text plus one palette colour token such as `cyan-700`, size `s`/`m`/`l`/`xl`, a unique set of `bold`/`italic`/`underline`/`lineThrough` styles and alignment); `visible` defaults to `true`, so a visible Description does NOT need `visible: true`. `title` is the wrapper title shown above the cards (default "Card group"). `appearance` is optional; omitting it keeps the Card group's canonical blank wrapper, and a `custom` backdrop takes a colour, gradient or one of the five preset background images (`azure`, `mira`, `solis`, `serenity`, `glow`). `layout` sets Customizer Width (2-6, default 4) and Height (Auto by default, a manual value is at least 50px). Per-card colours, the card gap and justification are customizer-only settings and are not accepted here, and neither are HTML, Markdown, CSS, Tailwind classes or raw bricks. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    async addPortalCardGroupBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/card-group",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalCardGroupBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Carousel block to a portal page
      * Stages one Customizer-compatible Carousel on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Carousel" tile. It creates exactly one flexible block with a single Carousel brick; no page, sidebar item or media asset is created. Omit `content` to get the Customizer default of three slides (Deliberation, Elaboration, Presentation) with their built-in images, descriptions, More buttons and links. `content.items` replaces that list entirely and must hold 1 to 6 slides in visual order; the slide index is taken from the array position and is not accepted from the caller. Each slide takes `caption` and `description` (plain text; only `description` supports the `{{ClientName}}` and `{{ClientLastName}}` variables), `button: {text}` or `null` for no Button, and `destination` or `null` for no link — an exact `pageId` of a page in THIS portal, an absolute https URL or an email address. The slide surface and its Button share that one destination. Every slide image is a built-in one: an image/video URL, asset id, file name, base64, local path or upload is rejected, as are a raw DynamicLink, raw item index, brick, CSS class, autoplay, duration, controls and indicators. Carousel has no public Appearance settings. `layout` sets Customizer 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.
@@ -146,6 +161,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Custom widget block to a portal page
+     * Stages one Customizer-compatible Custom widget on an EXISTING portal page — the programmatic equivalent of the customizer's Custom "Custom widget" tile. It creates exactly one flexible block of the `custom` template; no page, sidebar item or media asset is created. Omit `content` to get the Customizer default of the nine "Your Consultant" bricks. `content.bricks` replaces that list entirely and holds the bricks in visual order, each one of the seven kinds the Customizer's "Add block" palette offers: `heading`, `text`, `image`, `avatar`, `rating`, `link` and `button`. A field belonging to another brick kind is rejected rather than dropped. Every image is a built-in one: an image URL, asset id, file name, base64, local path or upload is rejected, as are a raw DynamicLink, a raw brick index, a CSS class and a theme override. A `link` brick needs a `destination`; a `button` brick without one is created unlinked and stays linkable in the Customizer. A destination is an exact `pageId` of a page in THIS portal, an absolute https URL or an email address. `title` and `appearance` set the Customizer Appearance section: omitting `appearance` keeps the widget's canonical `blank` backdrop with the title shown, and `background`, `padding` and `showTitle` apply only to `custom`. `layout` sets Customizer Width (2-6, default 2) 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.
+     */
+    async addPortalCustomWidgetBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/custom-widget",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalCustomWidgetBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Database block to a portal page
      * Stages one Customizer-compatible Database block on an EXISTING portal page — the programmatic equivalent of the customizer's "Database" tile. It creates exactly one flexible block with a single dashboard brick; no page, sidebar item, database, dashboard or view is created and the selected view's own settings are untouched. Both Customizer types are supported: `database` (Database -> Table -> View) and `dashboard` (a shared source such as All forms -> View). Pass exact ids from listPortalDatabaseBlockSources; names, aliases and URLs are rejected, and the dashboard must belong to `databaseId` in database mode. Optional `title` (default "Database"), `itemsPerPage` (10/20/50/100/200/500, default 100), `appearance` and `layout`. To change whether the view is editable call setDashboardViewReadonly separately — that is a global view setting. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -176,6 +206,36 @@ class PortalsApi {
             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.
+     */
+    async addPortalFileUploaderBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/file-uploader",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalFileUploaderBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Add a Form block to a portal page
+     * Stages one Customizer-compatible Form on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Form" tile. It creates exactly one flexible block with a Description brick and a Form content brick; no page, sidebar item, form response or file is created. The body may be empty, which reproduces the Customizer default: the title "Form", the contact-and-company description copy and five fields — required half-width First name, Last name and Contact email, optional half-width Project name and an optional full-width Project overview — plus a visible "Submit" button and reusable true. `content.form.fields` is the COMPLETE visual-order list: omit it to keep those five, or send [] for a Form without fields. Each field takes a `type` (text, textarea, number, phone, email, checkbox, select, file or date) and the optional `label`, `required` and `width` (`half`/`full`); `placeholder` is accepted only for text, textarea, number, phone, email and select, and `options` is a string array for select only — never the persisted newline-separated string. Field ids, indexes, column counts, raw bricks and renderer schema are rejected. Field labels, placeholders, options and the submit text are plain text without dynamic variables; the block `title` and the Description text accept `{{ClientName}}` and `{{ClientLastName}}`. `content.description` and `content.form` are hidden independently with `visible: false`. `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.
+     */
+    async addPortalFormBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/form",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalFormBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Text & Media Heading block to a portal page
      * Stages one Customizer-compatible Heading block on an existing portal page — the programmatic equivalent of the customizer's Text & Media "Heading" 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 Title Goes Here", size `l`, 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.
@@ -191,6 +251,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add an HTML/CSS block to a portal page
+     * Stages one Customizer-compatible HTML/CSS block on an EXISTING portal page — the programmatic equivalent of the customizer's Custom "HTML/CSS block" tile. It creates exactly one flexible block of the `code` template carrying a single code brick; no page, sidebar item or media asset is created. ONLY a portal served from a verified custom CNAME domain may carry one — on a Fusebase-owned portal subdomain the request is rejected with 400. (The Customizer's own HTML/CSS editors gate on the domain only and have a beta-programme escape hatch this operation does not honour, so a rejection here does not always mean the owner cannot do it in the UI.) Omit `content` to get the Customizer default demo (a "Sales Distribution" pie chart). `content` replaces that demo entirely and takes `html` (markup inserted as-is), `style` (raw CSS with no `<style>` tag, injected globally, so scope every rule with your own class names) and `script` (raw JavaScript with no `<script>` tag, run on every visit of the published page); an omitted field is empty rather than the demo value, and each is limited to 50000 characters. The code is stored verbatim and is NOT sanitized, so send only markup and scripts the portal owner asked for. The block's wrapper is pinned to the Customizer's own edge-to-edge one, which hides `title` BY DEFAULT; the owner can change the backdrop, padding and Show title in the Customizer's Appearance section afterwards, so this operation exposes no `appearance` field rather than a partial one. `layout` sets Customizer Width (2-6, default 3) 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), so the portal owner reviews the code before it goes live. Requires portals.write access.
+     */
+    async addPortalHtmlCssBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/html-css",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalHtmlCssBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Text & Media Image block to a portal page
      * Stages one Customizer-compatible Image block on an existing portal page — the programmatic equivalent of the customizer's Text & Media "Image" tile. It always creates the customizer's default stock image: `assetId`, `src`, a URL, base64, a file path or name, HTML and any other image input are rejected, and so are Appearance and text settings. Only `layout` applies. 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.
@@ -206,6 +281,51 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add an Info block to a portal page
+     * Stages one Customizer-compatible Info block on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Info block" tile: a compact clickable tile with one image, one title and one destination. No page, sidebar item or media asset is created, and it is NOT the Card tile (use addPortalCardBlock for that). Required `title` is the text shown inside the tile. Required `image` is exactly one semantic variant: `{type:"emoji", emoji}` with one visible Unicode emoji, `{type:"icon", iconId}` with an exact id from searchPortalInfoBlockIcons, or `{type:"custom", url}` with an existing absolute https image URL the user supplied — this operation uploads nothing and the internal `emoji#`/`icon#`/`url#` format is rejected. Required `destination` is an exact `pageId` of a page in THIS portal or an absolute https URL. Optional `openInNewTab` (default true) and `layout` set Customizer Width (1-3, default 1) and Height (Auto by default, a manual value is at least 50px); there is no row count. The Info block has no Appearance section: a backdrop, colour, padding, CSS or a raw wrapper is rejected. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    async addPortalInfoBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/info",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalInfoBlock",
+            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.
+     */
+    async addPortalKanbanBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/kanban",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalKanbanBlock",
+            expectedContentType: "application/json",
+        });
+    }
+    /**
+     * Add a Linked block to a portal page
+     * Stages one Customizer-compatible Linked block on an EXISTING portal page — the programmatic equivalent of the customizer's Custom "Linked block" tile. The block MIRRORS an existing block of another page: its title, width, height, wrapper and actions are taken from the source and it keeps following the source, so no title, layout, appearance or content is accepted here. `source` is the exact `portalId`/`pageId`/`blockId` triple from listPortalLinkableBlocks; never invent ids. Both portals must belong to this organization and the caller must be allowed to edit both. A block staged only in a draft can be linked ONLY within the same portal — a cross-portal source must already be published. A Linked block cannot point at another Linked block, nor at a block on the target page itself. The block is staged in the target portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    async addPortalLinkedBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/linked",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalLinkedBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add an existing Fusebase note as a block to a portal page
      * Embeds an existing Fusebase note as a content block on an existing portal page (no new page or sidebar item is created). The note must already exist in the portal's workspace and be shared into the portal (e.g. created via createPortalPageWithNote). Pass pageId (the target page node id, obtained from listPortalContent) and noteId. The block is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending block, and publishes it. Returns the created block id and the draft branch/seqs. Requires portals.write access.
@@ -221,6 +341,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a task list as a block to a portal page
+     * Creates a new Fusebase note, shares it into the portal, initialises a task list inside it and adds the note as a block to an existing portal page — the programmatic equivalent of the customizer's Project management "Task list" 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 and task list title, at most 100 characters, default "Task list") and layout (colspan 3-6, default 6; height in pixels or null for Auto, default null). The list starts empty — tasks are added by portal users, not by this operation, and an existing task list cannot be attached. 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/task list/block ids and the draft branch/seqs. Requires portals.write access.
+     */
+    async addPortalTaskListBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/task-list",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalTaskListBlock",
+            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.
@@ -236,6 +371,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Timeline block to a portal page
+     * Stages one Customizer-compatible Timeline block on an EXISTING portal page — the programmatic equivalent of the customizer's "Timeline" tile from Project management. Use it for a visual ordered sequence of project phases, milestones or steps with completion progress; it is NOT a Task list, Kanban, Carousel or Card group. It creates exactly one flexible block with four bricks (Image, Description, Step group, Button); no page, sidebar item or media asset is created. The body may be empty, which reproduces the Customizer default: the title "Timeline", the horizontal view, the built-in image, the project description, the completed Vision and Arrangements steps, the incomplete Launch step and a "View project" button. `view` is `horizontal` (default) or `vertical`. `title` is the wrapper title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `content.image.visible` shows or hides the BUILT-IN image; no image url, asset id, filename, base64 or local path is accepted. `content.description` takes `visible`, `text`, `color`, `size`, `styles` and `align`. `content.steps` REPLACES the whole step list with 1 to 6 steps in visual order; every step takes a `title` of at most 25 characters and may take `completed` and a `destination`, and completed steps must be consecutive from the first one. `content.button` takes `visible`, a plain `text` and a `destination`. A step or Button destination is an exact pageId in this SAME portal, an absolute https:// URL or an email address; raw DynamicLink fields are rejected. `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.
+     */
+    async addPortalTimelineBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/timeline",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalTimelineBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Invite multiple users to a portal in one call
      * Invites a batch of users to a single portal in one request, replacing N sequential inviteToPortal calls. Portal discovery (listPortals/getPortal) runs once for the whole batch. Invites are processed with bounded concurrency (default 5, max 5); the rest are queued. With background=false (default) the response waits for all invites and returns aggregated per-invitation results (status='completed'). With background=true the response returns immediately (status='processing') and invites run in the background without blocking the caller. Per-invitation orgRole/isFullAccess semantics match inviteToPortal. Invarian — before calling for client invites (orgRole='client' or unspecified): ALWAYS ask the user 'Full access (all pages) or Shared only (public pages)?' and wait for their answer.
@@ -473,6 +623,20 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Discover the blocks a Linked block can point at
+     * Read-only discovery of the exact source block ids addPortalLinkedBlock requires. Lists the blocks of ONE page over the published portal AND its active customizer draft, in display order, as `blocks` of `blockId`, `type`, `templateType`, `title` and `draftOnly`. A `draftOnly` block is staged but not published and may only be linked from a page in the SAME portal. Linked blocks are excluded — a Linked block cannot point at another one. The response carries identity only: never bricks, wrappers, content, data or draft events. Requires portals.write access.
+     */
+    async listPortalLinkableBlocks(params) {
+        return this.client.request({
+            method: "GET",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/linkable",
+            pathParams: params.path,
+            headers: params.headers,
+            opId: "listPortalLinkableBlocks",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * List organization portals
      * Returns portals visible for the caller in the organization. Requires portals.read and org access.
@@ -488,8 +652,8 @@ class PortalsApi {
         });
     }
     /**
-     * Publish a portal's staged draft
-     * Publishes all staged changes in the portal's customizer draft to the live portal, applying them through the same content pipeline the customizer's Publish button uses. Use this to make an agent's previously staged content/settings ops (folders, pages, blocks, access mode, custom code) visible to clients without opening the customizer. Returns 400 if the draft is empty and 409 if the portal was published elsewhere since the draft was based (refresh the draft first). Requires portals.write access.
+     * 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.
      */
     async publishPortalDraft(params) {
         return this.client.request({
@@ -501,6 +665,20 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Search the Portal Info block icon catalog
+     * Searches the icon catalog addPortalInfoBlock accepts — a versioned snapshot of the Customizer's own icon set. Call it before addPortalInfoBlock whenever the user asks for an Icon rather than an Emoji or a Custom image, and pass the returned exact `items[].id` as `image.iconId`; never derive an id from a label. `query` is optional (omit it to browse) and is matched against the icon id. Returns one bounded page of { id, label }, the matching `total`, and a nextCursor when more pages exist. The catalog is global and read-only: it is not scoped to an organization or portal, returns no SVG content, and changes nothing.
+     */
+    async searchPortalInfoBlockIcons(params) {
+        return this.client.request({
+            method: "GET",
+            path: "/portals/block-options/info-icons",
+            query: params.query,
+            headers: params.headers,
+            opId: "searchPortalInfoBlockIcons",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Restrict or allow editing of a dashboard view
      * The customizer's "Restrict editing" switch. This is a GLOBAL view setting, not a portal-block setting: it applies everywhere the view is used, including other portal blocks and the dashboard itself. Call it only when the user explicitly asks to restrict or allow editing; it is never part of addPortalDatabaseBlock. Requires dashboard.write access.
@@ -533,7 +711,7 @@ class PortalsApi {
     }
     /**
      * 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>). 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.
+     * 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.
      */
     async updatePortalCustomCode(params) {
         return this.client.request({

package/dist/types/isolated-store/isolated-store.d.ts

@@ -476,6 +476,65 @@ export interface IsolatedStoreSqlDeleteRequestContract {
 export interface IsolatedStoreSqlDeleteResponseContract {
     rowCount: number;
 }
+export type IsolatedStoreSqlBatchOperationKindContract = "query" | "execute" | "count" | "select" | "insert" | "batchInsert" | "update" | "delete";
+/**
+ * One step of a batch. Fields mirror the single-operation request of the same
+ * kind; only the ones that kind uses are read. `rlsContext` /
+ * `trustedRuntimeContext` are batch-level and cannot be set per operation.
+ */
+export interface IsolatedStoreSqlBatchOperationContract {
+    op: IsolatedStoreSqlBatchOperationKindContract;
+    /** `query` / `execute` only. */
+    sql?: string | null;
+    /** `query` / `execute` only. */
+    params?: unknown[] | null;
+    schemaName?: IsolatedStoreSqlSchemaNameInQueryOptional;
+    tableName?: string | null;
+    /** `select` only. */
+    columns?: string[] | null;
+    filters?: IsolatedStoreSqlFilterContract[] | null;
+    /** `select` only. */
+    sort?: IsolatedStoreSqlSortContract[] | null;
+    /** `select` only. */
+    limit?: number | null;
+    /** `select` only. */
+    offset?: number | null;
+    /** `insert` / `update` only. */
+    values?: Record<string, unknown> | null;
+    /** `batchInsert` only. */
+    rows?: Record<string, unknown>[] | null;
+    returning?: string[] | null;
+    /** `update` / `delete` only — required to mutate without filters. */
+    allowAll?: boolean | null;
+}
+export interface IsolatedStoreSqlBatchRequestContract {
+    operations: IsolatedStoreSqlBatchOperationContract[];
+    rlsContext?: IsolatedStoreSqlRlsContextContract | null;
+    trustedRuntimeContext?: IsolatedStoreSqlTrustedRuntimeContextContract | null;
+}
+/** Flat superset of the single-operation responses; populated per `op`. */
+export interface IsolatedStoreSqlBatchOperationResultContract {
+    op: IsolatedStoreSqlBatchOperationKindContract;
+    /** `query` / `execute`. */
+    result?: IsolatedStoreSqlQueryResultContract | null;
+    /** `count`. */
+    count?: number | null;
+    /** `select`. */
+    columns?: string[] | null;
+    /** `select` / `insert` / `batchInsert` / `update`. */
+    rows?: Record<string, unknown>[] | null;
+    /** `insert` / `batchInsert` / `update` / `delete`. */
+    rowCount?: number | null;
+    /** `select`. */
+    page?: {
+        limit: number;
+        offset: number;
+        rowCount: number;
+    } | null;
+}
+export interface IsolatedStoreSqlBatchResponseContract {
+    results: IsolatedStoreSqlBatchOperationResultContract[];
+}
 export interface CreateIsolatedStoreRequestContract {
     alias: string;
     storeType: IsolatedStoreTypeContract;
@@ -657,3 +716,13 @@ export declare const IsolatedStoreSqlImportFormatContract: {
     readonly Csv: "csv";
     readonly Tsv: "tsv";
 };
+export declare const IsolatedStoreSqlBatchOperationKindContract: {
+    readonly Query: "query";
+    readonly Execute: "execute";
+    readonly Count: "count";
+    readonly Select: "select";
+    readonly Insert: "insert";
+    readonly Batchinsert: "batchInsert";
+    readonly Update: "update";
+    readonly Delete: "delete";
+};

package/dist/types/isolated-store/isolated-store.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.IsolatedStoreSqlImportFormatContract = exports.IsolatedStoreSqlSortDirectionContract = exports.IsolatedStoreSqlFilterOperatorContract = exports.IsolatedStoreSqlMigrationIssueFieldContract = exports.IsolatedStoreSqlMigrationIssueCodeContract = exports.IsolatedStoreSqlRlsValidationWarningCodeContract = exports.IsolatedStoreSqlRlsTableClassificationContract = exports.IsolatedStoreSqlRlsWarningCodeContract = exports.IsolatedStoreScopeTypeContract = exports.IsolatedStoreRevisionKindContract = exports.IsolatedStoreStageStatusContract = exports.IsolatedStoreStatusContract = exports.IsolatedStoreEngineContract = exports.IsolatedStoreTypeContract = void 0;
+exports.IsolatedStoreSqlBatchOperationKindContract = exports.IsolatedStoreSqlImportFormatContract = exports.IsolatedStoreSqlSortDirectionContract = exports.IsolatedStoreSqlFilterOperatorContract = exports.IsolatedStoreSqlMigrationIssueFieldContract = exports.IsolatedStoreSqlMigrationIssueCodeContract = exports.IsolatedStoreSqlRlsValidationWarningCodeContract = exports.IsolatedStoreSqlRlsTableClassificationContract = exports.IsolatedStoreSqlRlsWarningCodeContract = exports.IsolatedStoreScopeTypeContract = exports.IsolatedStoreRevisionKindContract = exports.IsolatedStoreStageStatusContract = exports.IsolatedStoreStatusContract = exports.IsolatedStoreEngineContract = exports.IsolatedStoreTypeContract = void 0;
 exports.IsolatedStoreTypeContract = {
     Sql: "sql"
 };
@@ -92,3 +92,13 @@ exports.IsolatedStoreSqlImportFormatContract = {
     Csv: "csv",
     Tsv: "tsv"
 };
+exports.IsolatedStoreSqlBatchOperationKindContract = {
+    Query: "query",
+    Execute: "execute",
+    Count: "count",
+    Select: "select",
+    Insert: "insert",
+    Batchinsert: "batchInsert",
+    Update: "update",
+    Delete: "delete"
+};