Weaverse Content API

Read and edit live Weaverse content (projects, pages, theme settings, languages) outside the Studio editor, over an authenticated REST API. Use it for bulk edits, AI/automation content pipelines, and pushing updates into a project that already exists.

• Base URL: https://studio.weaverse.io/api/v1/content
• Machine spec: GET https://studio.weaverse.io/api/v1/content/openapi.json (OpenAPI 3.1, no auth) — the authoritative contract
• Full endpoint details: references/endpoints.md. Rich-text/Portable Text details: references/portable-text.md.
• Helper script: scripts/weaverse_content_api.mjs (zero-dependency, Node 18+).

The one thing you must understand first

The Content API edits live content — and it can also create pages.

Two write paths exist:

• PATCH .../pages/:type/*handle shallow-merges data into items on the page. Existing ids are updated; an unknown id is created when its entry also supplies a type (the component type). children may be supplied to relink an item's children in the same request — each entry needs an id that already belongs to the page or is created in the same request.
• POST /projects/:projectId/pages creates a page — a CUSTOM page (bespoke merchant page, blank root) or a resource-backed template page (PRODUCT/COLLECTION/PAGE/BLOG/ARTICLE, a per-resource override that clones the project's shared default template or a basedOn source page).

So the lifecycle is: