> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xenia.team/llms.txt
> Use this file to discover all available pages before exploring further.

# End Project

> Ends every schedule on the project. Tasks that already exist are untouched and remain readable and reportable — this is the non-destructive way to stop a recurring project. Send no request body. The response `data` is always an empty object.



## OpenAPI

````yaml PUT /api/v1/ops/workspaces/{workspaceId}/projects/{projectId}/end
openapi: 3.1.0
info:
  title: Xenia Team API - End Project
  version: 1.0.0
  description: >-
    Ends the project's schedules so no further tasks are generated, leaving the
    project and every task it already produced intact.
servers:
  - url: https://api.xenia.team
security: []
paths:
  /api/v1/ops/workspaces/{workspaceId}/projects/{projectId}/end:
    put:
      tags:
        - Projects
      summary: End Project
      description: >-
        Ends every schedule on the project. Tasks that already exist are
        untouched and remain readable and reportable — this is the
        non-destructive way to stop a recurring project. Send no request body.
        The response `data` is always an empty object.
      parameters:
        - name: workspaceId
          in: path
          required: true
          description: UUID of the workspace. Must be the workspace the API key belongs to.
          schema:
            type: string
            format: uuid
            example: cb363f7e-c52a-4478-911d-f6a6f791090e
        - name: projectId
          in: path
          required: true
          description: UUID of the project.
          schema:
            type: string
            format: uuid
            example: c7966d63-52ce-4967-b30a-16aaa9e806b5
      responses:
        '200':
          description: Project schedules ended successfully.
          content:
            application/json:
              example:
                data: {}
                extra_meta: {}
        '400':
          description: >-
            Bad Request - `Project is under processing`. The project's `state`
            is not yet `ready`, so its schedules cannot be changed.
        '401':
          description: >-
            Unauthorized - Invalid client credentials, or the key does not
            belong to this workspace.
        '403':
          description: >-
            Forbidden - API key not authorized for this route, the role lacks
            the required permission, the workspace does not have the Projects
            feature, or the project id is unknown to the caller. Note an unknown
            or deleted projectId also returns 403, not 404: the project access
            check runs before the handler and denies when it cannot load the
            project.
        '500':
          description: Internal Server Error.
      security:
        - clientKey: []
          clientSecret: []
components:
  securitySchemes:
    clientKey:
      type: apiKey
      in: header
      name: x-client-key
    clientSecret:
      type: apiKey
      in: header
      name: x-client-secret

````