page

Call page.publish_as_blueprint

Save one of this workspace's sites as a template to start new sites from — 'save this as a template', 'I want to reuse this layout', 'make this the starting point for the next one'. Save one of this workspace's sites as a reusable template, so new sites can be created from a copy of it with this brand's name and colours substituted in. It does NOT put anything on the internet — the site's own live address is unchanged — and it copies the site's most recent BUILT version, so a site that has never finished a build is refused. Pass blueprint_id only to update a template that already exists. Not for withdrawing a saved template — that is page.retire_blueprint. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/page.publish_as_blueprint

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/page.publish_as_blueprint
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

site_idstring uuid

The SITE the member means, as a site UUID. You are NOT shown the id of the site open on screen — it never appears in your context, so there is nothing to copy. When they say 'this site', 'the site I'm looking at', or name no site at all, they mean that on-screen site, and the way to reach it is: where this schema leaves site_id OPTIONAL, OMIT IT ENTIRELY — that is the primary path, not a fallback, and the turn's own surface resolves it server-side. Where the schema REQUIRES it, call page.list with name set to the site they named — it returns that one site's id, or the candidates to ask them about. Never pass a board, board-item, thread or any other id that merely happens to be nearby in the conversation — those name different objects and will be refused — and never one you composed.

namestring required

What the gallery calls this template. Unique within the workspace — a name already in use is refused, so ask the operator for another rather than inventing a variation.

descriptionstring

Optional one line on what the template is for, shown under its name.

blueprint_idstring uuid

Only when UPDATING a template that already exists — the saved blueprint's UUID, from page.list with list 'templates'. This re-points it at the site's newest built version. Leave it out to save a NEW template.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.