> ## 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 # Restore a version to live > Replaces live content with the content of one version. This overwrites what is live now, so it needs both `content:publish` and `content:delete`, and `confirm` must equal the `versionId` in the path (400 otherwise). - `type: "page"`: the version's page snapshot is written back to its page, using the assignment recorded on the version. Retired versions (listed by `?kind=retired-pages` on `GET /projects/{projectId}/versions`) can be restored the same way. A legacy version with no recorded assignment restores content only. - `type: "theme"`: the version's theme settings, preview host, default locale and recent colors are written to the project, and the project revision advances. **Conflicts (409 `CONFLICT`).** Another change to the same resource landed while restoring, or the version claims a resource binding the server cannot prove. Nothing is changed; `details.handle` names the resource. Retry after re-reading. **Cache.** If content was restored but edge delivery failed, the response includes `cacheDelivery: "degraded"`. Delivery stays queued and is retried without restoring again. Required scopes: `content:publish` and `content:delete` ## OpenAPI ````yaml https://studio.weaverse.io/api/v1/content/openapi.json post /versions/{versionId}/restore 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: /versions/{versionId}/restore: summary: Restore a version to live (content:publish + content:delete) description: >- Restoring overwrites live content, so it requires both publish and delete grants plus confirm="". parameters: - name: versionId in: path required: true schema: type: string post: tags: - Drafts and publishing summary: Restore a version to live description: >- Replaces live content with the content of one version. This overwrites what is live now, so it needs both `content:publish` and `content:delete`, and `confirm` must equal the `versionId` in the path (400 otherwise). - `type: "page"`: the version's page snapshot is written back to its page, using the assignment recorded on the version. Retired versions (listed by `?kind=retired-pages` on `GET /projects/{projectId}/versions`) can be restored the same way. A legacy version with no recorded assignment restores content only. - `type: "theme"`: the version's theme settings, preview host, default locale and recent colors are written to the project, and the project revision advances. **Conflicts (409 `CONFLICT`).** Another change to the same resource landed while restoring, or the version claims a resource binding the server cannot prove. Nothing is changed; `details.handle` names the resource. Retry after re-reading. **Cache.** If content was restored but edge delivery failed, the response includes `cacheDelivery: "degraded"`. Delivery stays queued and is retried without restoring again. Required scopes: `content:publish` and `content:delete` operationId: restoreVersion requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/RestoreBody' example: projectId: clz7prj0a1b2c3d4e5f6g7h8 type: page confirm: clz8hst3b5d7f9h1j3l5n7p9 responses: '200': description: Restored (cacheDelivery=degraded if edge delivery pending) content: application/json: schema: type: object example: object: version_restored versionId: clz8hst3b5d7f9h1j3l5n7p9 projectId: clz7prj0a1b2c3d4e5f6g7h8 '401': description: Missing or invalid credentials content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Foreign project or missing scope (INSUFFICIENT_SCOPE) content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: Not found (never discloses other tenants) content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: Concurrent claim; nothing changed — retry content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: RestoreBody: type: object required: - projectId - type - confirm properties: projectId: type: string type: type: string enum: - page - theme confirm: type: string description: Must equal the versionId 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.