> ## 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/*`.
> Before using any code sample, read `@weaverse/hydrogen` in the project's `package.json`: 6.x and 5.x import from different entries and use different type names, so code for one does not build on the other.
> `@weaverse/hydrogen` 6 (Shopify Hydrogen 2026.10 and later, the version these docs show) imports from `@weaverse/hydrogen/react-router` and uses `Weaverse*` types such as `WeaverseComponentProps`, `WeaverseComponentLoaderArgs` and `WeaverseComponentSchema`; the root `@weaverse/hydrogen` entry only exports `createSchema()`, data helpers and types.
> `@weaverse/hydrogen` 5.x (Hydrogen 2026.4 and earlier) imports everything from `@weaverse/hydrogen` and uses `HydrogenComponentProps`, `ComponentLoaderArgs` and `HydrogenComponentSchema`. On a 5.x project, convert samples to these names. Upgrade to 6 only when asked (`npx @weaverse/cli@latest migrate v6`, plus the Hydrogen 2026.10 upgrade). Do not mix major versions.
> Next.js themes use `@weaverse/hydrogen` 6.2.0 or later: import client and shared code from `@weaverse/hydrogen/next` and server-only code from `@weaverse/hydrogen/next/server`. `@weaverse/next` is deprecated; never install or import it.
> For live project data (pages, theme settings, translations), use the Weaverse MCP server: https://weaverse.io/docs/developer-tools/weaverse-mcp

# Bulk delete pages

> Deletes page assignments in a project and soft-deletes each underlying page once it has no remaining live assignments; assignments for other locales or resources keep a shared page live. Only assignments in the project named in the URL are touched.

Identify up to 500 targets with one selector per request:

- `pageIds`: page ids, scoped to this project.
- `handles` + `type`: handles of one page type, with an optional `locale`. When `locale` is omitted the legacy `en-us` locale is used; an empty string is rejected. For custom pages, pass the exact handle from the pages list, including any `/`.

If both `pageIds` and `handles` are present and `pageIds` is an array, `pageIds` wins and `handles` is ignored.

A `handles` request naming an internal template-marker handle (`isTemplateMarker: true` on the pages list) is rejected with `400` and deletes nothing, so a bulk delete can never half-apply and strip a custom template's wiring. Delete such a template by its `pageIds` instead.

Deletion is consequential: resolve targets with the pages list first and, when acting through an agent, confirm them with the user. Use the response counts and handle lists to find misses (`notFound`) or per-page failures (`failed`).

Clients or CDNs that strip `DELETE` bodies may send `POST` to the same URL with the same body.

Required scope: `content:write` and `content:delete`. A credential with a stored scope list (any delegated grant or a shop API key minted with scopes) without `content:delete` gets `403 INSUFFICIENT_SCOPE` and nothing is deleted. Only shop API keys minted before scopes existed keep this endpoint's historical delete access.



## OpenAPI

````yaml https://studio.weaverse.io/api/v1/content/openapi.json delete /projects/{projectId}/pages
openapi: 3.1.0
info:
  title: Weaverse Content API
  version: 1.0.0
  description: >-
    Authenticated REST API for reading and editing Weaverse-managed content
    (projects, pages, drafts, global sections, theme settings, languages) and
    for reading and writing per-locale translations.


    ## Authentication


    Send a bearer token in the `Authorization` header: a shop API key
    (`WEAVERSE_API_KEY`), a scoped API key or a delegated MCP OAuth token.
    Translation-unit routes also accept a project-bound translation agent token.
    Each operation's description ends with the scope it requires.


    ## Scopes


    | Scope | Grants |

    |---|---|

    | `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 or cancel
    publications, restore versions, publish global sections |

    | `content:delete` | Delete pages, global sections, languages and static
    keys, and revert overrides. Project deletion also needs `project:manage` |

    | `project:manage` | Create, copy and delete projects; settings, variants,
    hierarchy, backups, restore as new, previews and hostname policy |

    | `translations:read` | Read translation units only, with no general content
    access |

    | `translations:write` | Apply translation units only; never changes page
    content |


    A legacy API key without scopes keeps read, write and translation access and
    every endpoint that existed before scopes, but never gains publish, delete
    or project management.
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}/pages:
    delete:
      tags:
        - Pages
      summary: Bulk delete pages
      description: >-
        Deletes page assignments in a project and soft-deletes each underlying
        page once it has no remaining live assignments; assignments for other
        locales or resources keep a shared page live. Only assignments in the
        project named in the URL are touched.


        Identify up to 500 targets with one selector per request:


        - `pageIds`: page ids, scoped to this project.

        - `handles` + `type`: handles of one page type, with an optional
        `locale`. When `locale` is omitted the legacy `en-us` locale is used; an
        empty string is rejected. For custom pages, pass the exact handle from
        the pages list, including any `/`.


        If both `pageIds` and `handles` are present and `pageIds` is an array,
        `pageIds` wins and `handles` is ignored.


        A `handles` request naming an internal template-marker handle
        (`isTemplateMarker: true` on the pages list) is rejected with `400` and
        deletes nothing, so a bulk delete can never half-apply and strip a
        custom template's wiring. Delete such a template by its `pageIds`
        instead.


        Deletion is consequential: resolve targets with the pages list first
        and, when acting through an agent, confirm them with the user. Use the
        response counts and handle lists to find misses (`notFound`) or per-page
        failures (`failed`).


        Clients or CDNs that strip `DELETE` bodies may send `POST` to the same
        URL with the same body.


        Required scope: `content:write` and `content:delete`. A credential with
        a stored scope list (any delegated grant or a shop API key minted with
        scopes) without `content:delete` gets `403 INSUFFICIENT_SCOPE` and
        nothing is deleted. Only shop API keys minted before scopes existed keep
        this endpoint's historical delete access.
      operationId: deletePages
      parameters:
        - name: projectId
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              oneOf:
                - type: object
                  required:
                    - pageIds
                  properties:
                    pageIds:
                      type: array
                      items:
                        type: string
                      maxItems: 500
                - type: object
                  required:
                    - handles
                    - type
                  properties:
                    handles:
                      type: array
                      items:
                        type: string
                      maxItems: 500
                    type:
                      type: string
                    locale:
                      type: string
                      description: Optional. Defaults to the stored default locale.
            example:
              type: CUSTOM
              handles:
                - pages/old-campaign
                - pages/expired-offer
              locale: en-us
      responses:
        '200':
          description: Delete result with per-target accounting
          content:
            application/json:
              schema:
                type: object
                properties:
                  object:
                    type: string
                    enum:
                      - page_delete
                  requested:
                    type: integer
                  deleted:
                    type: integer
                  notFound:
                    type: integer
                  failed:
                    type: integer
                  deletedHandles:
                    type: array
                    items:
                      type: string
                  notFoundHandles:
                    type: array
                    items:
                      type: string
                  failedHandles:
                    type: array
                    items:
                      type: string
              example:
                object: page_delete
                requested: 2
                deleted: 1
                notFound: 1
                failed: 0
                deletedHandles:
                  - pages/old-campaign
                notFoundHandles:
                  - pages/expired-offer
                failedHandles: []
        '400':
          description: Invalid params
          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
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
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 token: a shop API key (`WEAVERSE_API_KEY`), a scoped API key or a
        delegated MCP OAuth token; translation-unit routes also accept a
        project-bound translation agent token. Each operation lists the scope it
        requires; the scope table is in the API description.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.