> ## Documentation Index > Fetch the complete documentation index at: https://weaverse.io/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Weaverse component configuration uses `settings`. `inspector` is deprecated; never generate it. > Weaverse Hydrogen themes use React Router v7: import from `react-router`, never `react-router-dom` or `@remix-run/*`. > Define component schemas with `createSchema()` from `@weaverse/hydrogen` (React Router themes) or `@weaverse/next` (Next.js themes). > These docs cover @weaverse/hydrogen, @weaverse/react and @weaverse/core 5.x, and @weaverse/next 1.x. Do not use APIs from other major versions. > For live project data (pages, theme settings, translations), use the Weaverse MCP server: https://docs.weaverse.io/developer-tools/weaverse-mcp # Update project > Renames a project. This endpoint does not create, delete or reconfigure projects. - Only `name` is writable: a non-empty string of at most 191 characters. - Unknown fields are rejected with `400 INVALID_PARAMS` rather than silently ignored. - Send `expectedUpdatedAt` (the `revision` from GET) to fence the rename: if the project changed since that read, the call returns `409 STALE_PROJECT` instead of overwriting a newer name. Shop API keys may omit it; delegated (MCP OAuth) tokens must send it or get `428 PRECONDITION_REQUIRED`. - Hierarchy, shop linkage and market settings belong to Studio and the Dashboard and are not writable with an API key. - No cache invalidation happens: `name` does not affect rendered storefront content. - Clients or proxies that cannot send `PATCH` may send `POST` to the same URL with the same body. Required scope: `content:write` ## OpenAPI ````yaml https://studio.weaverse.io/api/v1/content/openapi.json patch /projects/{projectId} openapi: 3.1.0 info: title: Weaverse Content API version: 1.0.0 description: >- Authenticated REST API for querying Weaverse-managed content (projects, pages, theme settings, languages) and for reading and writing per-locale translations. servers: - url: https://studio.weaverse.io/api/v1/content description: Production security: - bearerAuth: [] tags: - name: Projects description: List, read, rename, create, copy and delete projects. - name: Pages description: List, read, create, update and delete the pages of a project. - name: Drafts and publishing description: >- Edit page drafts, then publish, schedule, restore and manage page versions. - name: Global sections description: Read, edit and publish sections shared across pages. - name: Page settings description: Read and edit page-level settings such as SEO metadata. - name: Assignments description: Map Shopify resources and routes to Weaverse pages and templates. - name: Theme settings description: Read and update a project's theme settings. - name: Languages and localization description: List project languages and manage locales, static text and glossary. - name: Translations description: >- Read and write per-locale translations, built for external translation agents. - name: Project structure description: Manage project variants and the project hierarchy. - name: Backups and portability description: Back up, restore, export and import project content. - name: Previews and hostnames description: Create preview links and manage the hostnames a project accepts. - name: Specification description: This OpenAPI document. paths: /projects/{projectId}: patch: tags: - Projects summary: Update project description: >- Renames a project. This endpoint does not create, delete or reconfigure projects. - Only `name` is writable: a non-empty string of at most 191 characters. - Unknown fields are rejected with `400 INVALID_PARAMS` rather than silently ignored. - Send `expectedUpdatedAt` (the `revision` from GET) to fence the rename: if the project changed since that read, the call returns `409 STALE_PROJECT` instead of overwriting a newer name. Shop API keys may omit it; delegated (MCP OAuth) tokens must send it or get `428 PRECONDITION_REQUIRED`. - Hierarchy, shop linkage and market settings belong to Studio and the Dashboard and are not writable with an API key. - No cache invalidation happens: `name` does not affect rendered storefront content. - Clients or proxies that cannot send `PATCH` may send `POST` to the same URL with the same body. Required scope: `content:write` operationId: updateProject parameters: - name: projectId in: path required: true schema: type: string requestBody: required: true content: application/json: schema: type: object required: - name additionalProperties: false properties: name: type: string minLength: 1 maxLength: 191 description: New project name. expectedUpdatedAt: type: string format: date-time description: >- The project `revision` from your last GET, sent back unchanged. When it no longer matches, the rename is refused with `409 STALE_PROJECT`. Optional for shop API keys; required for delegated (MCP OAuth) tokens, which get `428 PRECONDITION_REQUIRED` without it. example: name: Holiday Storefront expectedUpdatedAt: '2026-10-12T09:41:07.000Z' responses: '200': description: The updated project content: application/json: schema: type: object properties: object: type: string enum: - project id: type: string name: type: - string - 'null' parentProjectId: type: - string - 'null' createdAt: type: - string - 'null' format: date-time revision: type: - string - 'null' format: date-time description: >- The project's revision (its `updatedAt`). Send it back as `expectedUpdatedAt` on project-fenced writes such as a rename. example: object: project id: clz1k8m2n0000abcd1234efgh name: Holiday Storefront parentProjectId: null createdAt: '2026-01-15T08:30:00.000Z' revision: '2026-10-20T10:15:00.000Z' '400': description: Invalid body (missing/empty `name`, unknown fields, or invalid JSON) content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Project not found content: application/json: schema: $ref: '#/components/schemas/Error' '405': description: Method not allowed (use PATCH or POST) content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: >- STALE_PROJECT: the project changed after `expectedUpdatedAt` was read. Re-read the project and retry with its current `revision`. content: application/json: schema: $ref: '#/components/schemas/Error' example: object: error code: STALE_PROJECT message: >- This project changed after it was read. Reload before renaming. status: 409 '428': description: >- PRECONDITION_REQUIRED: a delegated (MCP OAuth) token omitted `expectedUpdatedAt`. content: application/json: schema: $ref: '#/components/schemas/Error' example: object: error code: PRECONDITION_REQUIRED message: >- "expectedUpdatedAt" is required for delegated writes: read the current content first and pass it so the write targets exactly what was read. status: 428 components: schemas: Error: type: object required: - object - code - message - status properties: object: type: string enum: - error code: type: string enum: - UNAUTHORIZED - FORBIDDEN - INSUFFICIENT_SCOPE - PROJECT_NOT_FOUND - PAGE_NOT_FOUND - STALE_PAGE - STALE_PROJECT - STALE_TRANSLATION - TRANSLATION_UNIT_NOT_FOUND - SERVICE_UNAVAILABLE - CONFLICT - PRECONDITION_REQUIRED - INVALID_PARAMS - INTERNAL_ERROR message: type: string status: type: integer details: description: >- Optional machine-readable context, for example the clashing handles of a 409 CONFLICT. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: WEAVERSE_API_KEY description: >- Bearer authentication: a shop API key (WEAVERSE_API_KEY), a scoped API key, a delegated MCP OAuth token, or (translation-unit routes only) a project-bound translation agent token. Scopes: content:read — Read projects, pages, theme settings, versions, drafts and translation units. content:write — Save drafts and make non-destructive edits (page items, metadata, SEO, assignments, languages, glossary). Never publishes or deletes. content:publish — Publish drafts, schedule/reschedule/cancel publications, restore versions, publish global sections. content:delete — Delete pages, global sections, languages, static keys, override reverts; required with project:manage for project deletion. project:manage — Create/copy/delete projects, settings, variants, hierarchy, backups, restore-as-new, previews, hostname policy. translations:read — Read translation units only (no general content access). translations:write — Apply translation units only; never mutates page content. A legacy unscoped API key keeps read/write/translation baseline access and every pre-scope endpoint, but never gains publish/delete/project-manage implicitly. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.